Fábio Cabrita

Fábio Cabrita on MC-95649 2016-05-25T15:59:04Z

It seems that i get a WORK AROUND for this bug!

I believe that this bug comes from previous version as 1.7 and before that, since i already had some problems, passing from 1.7 to 1.8, where we had some mobs spawning inside of blocks, and get some warning about it (dont remember the name of it). In that time we had executed the kill command, and we where able to solve the problem.

My server maps (overworld and nether) where generated in 1.6.2, back in setember of 2013.

So, to solve this, i started in last stable version, the 1.8.9 and edit the server.properties file, in the following lines, to avoid any type of spawning mobs:

difficulty=0 # with spawn-monsters=false this command does nothing but i had it in 0 at the time, because i was doing other tests before without sucess.
spawn-monsters=false
spawn-npcs=false
spawn-animals=false

Then i made a trip where i had "civilization" in all worlds, where we had mobs with alternative names. After that, i update my server to 1.9.4, and i notice some warnings (but serious less than before) of 'keeping entity', with all the spawning parameters in false⚠️ , and i executed the kill command through the uuid (/kill <mob uuid>) of the mobs in the warnings, some of them it was possible to kill. After doing this, i reach a point where i didnt get any warnings anymore, in the areas where i had before. Then i change again the spawn parameters:

difficulty=2
spawn-monsters=true
spawn-npcs=true
spawn-animals=true

And made again another trip in my worlds, and it was all fine, without any warnings. Now i just have to repopulate all the farms that i had working with mobs before through creative mode.

Its better then a full reset !!!!! =D

Hope that this could help you guys.
Cheers from Portugal.

Fábio Cabrita on MC-95649 2016-05-18T16:27:57Z

How can be that no one have yet started to repair this critical bug for old worlds, and are already adding more stuff in the game to prepare it to 1.10!!!!

I am playing in a server with almost 3 years old with my friends, and me and my friends have each one has an youtube channel where we post the meanwhile of our lifes in the game, and we are unable to update the server because of this bug. Each one of us have an average of 40 days of playing in this world, we are not playing around here!

If we have to reset our world, at least me will quit from playing minecraft for real!

Fábio Cabrita on MC-95649 2016-05-09T01:18:22Z

I had this problem after i made an upgrade on my server from 1.8.9 to 1.9. I am receiving tons of warnings about entitys with certain uuids, and i cannot remove them through command lines (/kill <mob uuid>, /kill @e[type=<mob name>] and /kill @e[!Player]), it seems that the same uuid is not removable from the list, and i have a lot of mobs in this situation. It says that i have killed the mob but after some time it happers again. This result in CPU usage of almost 100%, and after a while, it crashs, and the server restarts.

18:12:25 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:12:25 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:12:25 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:12:25 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:12:25 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:12:49 CONSOLE: [INFO] Killed Horse
18:13:18 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:18 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:18 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:18 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:18 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:45 CONSOLE: [INFO] Killed Horse
18:13:56 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:56 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:56 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:56 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:13:56 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:14:13 CONSOLE: [INFO] Killed Horse
18:14:42 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:14:42 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:14:42 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:14:42 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:14:42 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:15:24 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:15:24 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:15:24 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:15:24 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28
18:15:24 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

Fábio Cabrita on MC-98027 2016-03-09T20:59:41Z

I had this problem after i made an upgrade on my server from 1.8.9 to 1.9. I am receiving tons of warnings about entitys with certain uuids, and i cannot remove them through command lines (/kill <mob uuid>, /kill @e[type=<mob name>] and /kill @e[!Player]), it seems that the same uuid is not removable from the list, and i have a lot of mobs in this situation. It says that i have killed the mob but after some time it happers again. This result in CPU usage of almost 100%, and after a while, it crashs, and the server restarts.

18:12:25 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:12:49 CONSOLE: [INFO] Killed Horse

18:13:18 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:13:45 CONSOLE: [INFO] Killed Horse

18:13:56 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:14:13 CONSOLE: [INFO] Killed Horse

18:14:42 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

18:15:24 CONSOLE: thread/WARN]: Keeping entity EntityHorse that already exists with UUID 24ec0e25-2c6e-45b6-acae-d3754afc8a28

Fábio Cabrita on MC-63590 2014-09-30T12:29:55Z

Since i am getting the same problem, i made some tests with 1 gig of RAM, it crashs with just one player, and CPU and RAM are always on 100%.
There is no difference playing using 512 megas or 1024 megas.

Fábio Cabrita on MC-72314 2014-09-30T12:27:54Z

I made some tests with 1 gig of RAM, it crashs with just one player, and CPU and RAM are always on 100%.

There is no difference playing using 512 megas or 1024 megas.

Fábio Cabrita on MC-72314 2014-09-24T11:11:48Z

I beleave that, but it must be an huge increase of RAM usage now on 1.8.

How can be a duplicated of an issue that is happening with 1.7.5, since we have played that version before and didnt had any problem like these one in 1.8?

Fábio Cabrita

Assigned

Reported

Comments