Jerry Hundric
Assigned
Reported
Comments
Just by double-clicking "Minecraft_server.exe". No parameters as far as I know.
That's exactly what I saw in the crash report but before I manually triggered a crash, Minecraft was telling me that it was using over 700MB which would slowly increase to over 90% memory usage. Then the game would freeze for some time before going back to 700MB memory usage which would then again slowly increase to over 90%.
Even after saving and exiting the current world and loading another one Minecraft was still telling me that it was using 700MB and I still got random freezes when memory usage was over 90%
I spawned around about 10000 to 20000 mobs but if I allow Minecraft to use 4GB of RAM, it reports itself using 2GB of RAM after all the mobs are gone. I didn't spawn all the mobs at once because that would cause the game to lag heavily. I will probably have to take a few screenshots showing the exact problem.
I have attached a crash report after spawning and killing lots of mobs.
Can someone reopen MC-20278. The problem is that the code doesn't prevent the sending of the singal to place null blocks. Its also due to different code being used to send the actual message to place the block in the world. The solution I found was to move some code to a place just before the message is sent so that these messages to place null blocks aren't even produced in the first place.