On my unmodified server I encountered a server crash triggered by hostile mobs spawning with no perceivable upper limit.
One of my regular players has 2 mob spawners that empty into a single area. The spawners are a sekeleton spawner and a cave spider spawner. Before 1.8.3 the server would cap mob generation at a certain point but in this scenario that cap appears to have been ignored. The player left the game to run and within 30 minutes enough mobs had spawned to crash the game. Restarting the server to clear them out showed that 641 hostile mobs had been allowed to spawn while a single player was online.
It is worth noting that in the past this setup has been able to function without spawning out of control and did not result in enough lag to invoke the server watchdog to kill the server as happened here.
I have attached the crash report generated by the server with the player names removed.
Related issues
duplicates
Attachments
Comments
migrated
migrated
Dupe of MC-63590
migrated
@@unknown MC-63590 is the end result caused by the excessive mob spawning described above. This bug focuses on the root cause. To me the crash is probably preferable to letting mob spawn continue out of control. In either case the server is rendered unusable as a result of the underlying mob spawn issue which this bug seeks to address. This is not a dupe of the crash bug.
migrated
Well, unfortunately, it is.
The server watchdog causes a crash if there is too much lag on the server, which is usually caused by user fault. In this case, you.
If you want to turn off the watchdog, set the max-tick-time value in server.properties to a value higher than 60,000 or -1.
migrated
@@unknown I understand why the watchdog functions as it does. I also understand that this is related to the user's decision to allow his mob spawner to run out of control. The reason why I have filed this bug is because in the past mob generation appeared to be capped but that no longer seems to be the case. The player expected Minecraft to stop spawning mobs as it has always done in the past but it failed to do so. I see no indication that this cap has been officially removed so I must assume that it is a bug until ruled otherwise by Mojang. I appreciate your help but your suggestion still does not address the root cause.
migrated
Duplicate of MC-63590 – If you have not, please use the search function in the future, to see if your bug has already been submitted.
For technical support, please use the Mojang Support Center.
--- This action was performed automagically. If you believe this was done erroneously, please :light_bulb_on: raise an issue.