[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 Created: 05/Jan/13 Updated: 16/Feb/13 Resolved: 16/Feb/13 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.4.6 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Alex Green | Assignee: | Unassigned |
| Resolution: | Invalid | Votes: | 0 |
| Labels: | crash | ||
| Environment: |
Windows 7, Professional, 32 bit HP Desktop this is the machine i run the server on, and have a fixed local address to port forward to |
||
| Attachments: |
|
| Confirmation Status: | Unconfirmed |
| Description |
|
Put the summary of the bug you're having here What I expected to happen was...: What actually happened was...: Steps to Reproduce: |
| Comments |
| Comment by Alex Green [ 07/Jan/13 ] |
|
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 |
| Comment by Alex Green [ 07/Jan/13 ] |
|
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 |
| Comment by Anon Ymus [ 07/Jan/13 ] |
|
I think this should be resolved as invalid due to the fact that minecraft is not meant to be run with so little memory. |
| Comment by Alex Green [ 06/Jan/13 ] |
|
I ran it with the batch file noted above and it continues to crash with an |
| Comment by Alex Green [ 06/Jan/13 ] |
|
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 |
| Comment by Kumasasa [ 06/Jan/13 ] |
|
Ok, does the original issue still persist ? |
| Comment by Kumasasa [ 06/Jan/13 ] |
|
Now you've limited the maximum memory to 512M too. java -Xmx1g -Xms512M -cp Minecraft.exe net.minecraft.LauncherFrame Why don't you simply use the default launcher ? |
| Comment by Alex Green [ 06/Jan/13 ] |
|
here is the crash report generated running the minecraft.exe from the desktop without the batch file |
| Comment by Alex Green [ 06/Jan/13 ] |
|
i attached the crash report generated when running the batch file (pasted from the minecraft faq troubleshooting out of memory issues) 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 this crash only started recently, before this there was no issue with graphic card or opengl - has something changed here? |
| Comment by Kumasasa [ 06/Jan/13 ] |
|
You should assign minimum memory to the JVM ( -Xms512m ), you have no minimum. And get an update of your graphics drivers |
| Comment by Alex Green [ 06/Jan/13 ] |
|
these crashes have only started in the last few weeks on this machine. I suspect since 1.4.5 or 1.4.6 update |
| Comment by Kumasasa [ 05/Jan/13 ] |
|
It's not an out-of-memory-issue. Stack: [0x4ccc0000,0x4cd10000], sp=0x4cd0f50c, free space=317k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [KERNELBASE.dll+0xc6e3]
C [ig4icd32.dll+0x781403]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.lwjgl.opengl.GL11.nglDeleteLists(IIJ)V+0
j org.lwjgl.opengl.GL11.glDeleteLists(II)V+16
j arx.b(I)V+19
j bav.f()V+4
j net.minecraft.client.Minecraft.f()V+10
Please force a crash by pressing F3 + C for 10 seconds while ingame and attach the crash report here, there is more information in a Minecraft crash report. |