Alex Green
Assigned
Reported
MC-191674
End terrain not generating correctly. Eg at X 524273 Y100 Z 2285288 on any seed
Duplicate
MC-189871
Piglins don't run from soul fire when attacking the player
Duplicate
MC-189869
Baby hoglins and baby piglins run from player in creative mode.
Invalid
MC-189069
Lodestone compass flashy bug and no way to reset the compass when used on lodestone.
Duplicate
MC-188764
In creative mode 3 food items are missing from the food menu.
Duplicate
MC-188226
When traveling on soul sand with soul speed it increases Fov to extreme levels past 90 to quake pro.
Duplicate
MC-6169
crash due to running out of memory, already using batch file to limit to 512, system monitor showing javaw.exe keeps grabbing more memory until all is gone
Invalid
Comments
it has been stable playing now for 20 minutes, in the past it didnt last beyond 2 minutes before the memory was taken
i also just checked running through launcher (and javaw.exe) and the memory grabbing seems to be stabilising and not crashing
not sure what has changed....!
not sure if my issue is fixed - or the problem is just hiding
I ran it with the batch file noted above and it continues to crash with an
"Out of Memory" error
yes the crash from the launcher persists .....
thats why i went to the recommended batch file
when i let it crash, i cant find a crash report to post
here is the crash report generated running the minecraft.exe from the desktop without the batch file
i attached the crash report generated when running the batch file (pasted from the minecraft faq troubleshooting out of memory issues)
here is the content of that batch file
javaw -Xmx512m -Xms512m -jar minecraft.exe
I will also post a new forced crash report when I run it without the batch file
I did update the graphic drivers from the intel site before I posted this as an error
It is 9.17.10.2867 dated 26/09/2012
this crash only started recently, before this there was no issue with graphic card or opengl - has something changed here?
these crashes have only started in the last few weeks on this machine. I suspect since 1.4.5 or 1.4.6 update
anon ymus the original crashes were from running in the default launcher with no extra parameters
minecraft was crashing after it had taken over 1.3gb (based on what task manager was reporting)
the java dk was reporting much lower usage of memory by minecraft