Recently, I noticed a HUGE frame drop in a certain area of my world (not only in one chunk), the game even freezes completely and the FPS fluctuates between 1 and my normal 60 FPS..
One thing is for sure, it isn't caused by a surplus of entities, as it seems to happen in an area where the entity count is only around 100 (after switching to pieceful to get rid of egg holding zombies who may be causing this).
I forced a crash with F3+C and attached the report. I hope this can be resolved..
Linked issues
Attachments
Comments 12
Nothing jumps out at me from the crash report. Can you upload the affected world, either by attaching it to the ticket, or uploading it somewhere else and linking to it? The contents of the development console may also be helpful in diagnosing this issue.
You have Java 1.8.0_20-ea running, this is an alpha or beta version. Please install the latest release 1.8.0_05 from http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
That's so strange..
I attached the output of the development console when I force a crash. This line seems suspicious:
Client> [23:26:30] [Client thread/INFO]: Warning: Clientside chunk ticking took 666 ms
Did some research and found this bug: MC-44801 , where somebody said "this is a highly documented issue with timers, dispensers, or water falls, where if the client is just moving out of "render distance" range from one of those active areas, they will experience lag as the game fails to unload the active chunk."
I think this is exactly what happens. I have a mob farm which uses water dispenser (controlled by a clock).
My render distance was set to 8, because I like the fog this creates and my PC isn't the best. I set it to 10 now, and the lag disappeared. So I guess this is some sort of "fix" for now, but I really hope the problem itself gets solved soon!
Are you saying that the problem no longer occurs at all with render distance set to 10? Have you tried moving further away? Because @unknown's comment on MC-44801 says that changing the render distance didn't solve it for him, just changed the range at which the bug occurred.
14w21b:
I am definitively not an expert but I am not sure what is this: