I have 32 gigs of ram yet MINECRAFT 1.5.1 is now causing OUT OF MEMORY errors to occur. 1.4.7 does not. So 1.5.1 has, or seems to have, a serious memory leak issue.
No mods, stock game, survival single player, and survival multiplayer games are affected.
Modded games are also affected albeit slower than non modded games.
I am running MC with 8 gigs of ram for non modded, and 16 gigs for modded. I swapped non modded to 16 gigs and still, after about 30 minutes of game play, I begin to get out of memory errors.
I believe raymond has 64-bit, by looking at his signature.
Yes, it is by that, that I have pulled the conclusion that he might not have the 64-bit version of Java. Just because he has 64bit Windows, it does not mean he has 64bit Java.
Thanks. System is 64x, so is java. System is clean of malware and other pests. I am not a novice.
The problem is clearly a memory leak issue. MC hasn't crashed as of yet, just becomes so laggy that it becomes unplayable and my system provides the out of memory warning. I am using Opti-Fine (latest for 1.5.1). I have reinstalled Java 7 with current update. No joy. I use magic launcher to swap between Jar files 1.4.7 and 1.5.1. I also use the magic launcher to set the memory for MC.
1.5.1 is an incredible memory hog. 1.4.7 has no such issue.
I'm having sort of the same problem. Usually the memory will slowly creep up and eventually just dump like normal. Eventually it will just skyrocket and keep dumping the memory at very high rates. It doesn't become laggy for me, but eventually the allocated memory will reach the used memory and Minecraft just closes out. I don't get a crash screen or anything. At first I thought it was something with the mods I had installed, but even with a clean minecraft and running the default settings it will still eventually use a ton of memory.
edit: I also completely uninstalled Java and installed it again. 64-bit
When I run with the more memory batch file I get these errors if that helps.
Although now that I think about it those my be in my big inaccessable void. My guess is that the world file is corrupt. Does anyone else having this issue have the big void area? (check my thread if you don't know what I'm talking about)
2013-04-13 09:42:21 [SERVER] [SEVERE] Wrong location! qi['Chicken'/857, l='New W
orld', x=-235.41, y=69.00, z=-95.49]
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Unknown Source)
at abw.a(SourceFile:504)
at aab.a(SourceFile:1360)
at iz.a(SourceFile:508)
at aab.g(SourceFile:1314)
at aab.h(SourceFile:1221)
at iz.h(SourceFile:390)
at net.minecraft.server.MinecraftServer.r(SourceFile:462)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at bjh.q(SourceFile:122)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)
2013-04-13 09:42:21 [SERVER] [SEVERE] Wrong location! qi['Chicken'/893, l='New W
orld', x=-227.08, y=51.00, z=-93.08]
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Unknown Source)
at abw.a(SourceFile:504)
at aab.a(SourceFile:1360)
at iz.a(SourceFile:508)
at aab.g(SourceFile:1314)
at aab.h(SourceFile:1221)
at iz.h(SourceFile:390)
at net.minecraft.server.MinecraftServer.r(SourceFile:462)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at bjh.q(SourceFile:122)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)
2013-04-13 09:42:21 [SERVER] [SEVERE] Wrong location! qi['Chicken'/927, l='New W
orld', x=-230.48, y=69.00, z=-86.39]
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Unknown Source)
at abw.a(SourceFile:504)
at aab.a(SourceFile:1360)
at iz.a(SourceFile:508)
at aab.g(SourceFile:1314)
at aab.h(SourceFile:1221)
at iz.h(SourceFile:390)
at net.minecraft.server.MinecraftServer.r(SourceFile:462)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at bjh.q(SourceFile:122)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)
2013-04-13 09:42:21 [SERVER] [SEVERE] Wrong location! qi['Chicken'/928, l='New W
orld', x=-225.15, y=54.00, z=-92.85]
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Unknown Source)
at abw.a(SourceFile:504)
at aab.a(SourceFile:1360)
at iz.a(SourceFile:508)
at aab.g(SourceFile:1314)
at aab.h(SourceFile:1221)
at iz.h(SourceFile:390)
at net.minecraft.server.MinecraftServer.r(SourceFile:462)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at bjh.q(SourceFile:122)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)
I've done some troubleshooting and it looks like the saved world was corrupt. Starting a new world fixed my out of memory issues. Most likely you have a void in your map like I did causing a memory leak. What I mean by void is an area that the blocks wont populate in, it's blak and empty, but you can see the bottom, and you cannot access it either from above (by dropping in) or by digging your way from the side.
No mods, stock game, survival single player, and survival multiplayer games are affected.
Modded games are also affected albeit slower than non modded games.
I am running MC with 8 gigs of ram for non modded, and 16 gigs for modded. I swapped non modded to 16 gigs and still, after about 30 minutes of game play, I begin to get out of memory errors.
MC v1.5 - Win 7 SP1 64 bit - Intel I5 6970k - Gigabyte Z97X-UD5H-BK
16 Gigs Corsair Vengeance DDR3 - EVGA GTX 770 - Seagate SSD (240 Gig)
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Retired StaffI believe raymond has 64-bit, by looking at his signature.
My Github ด้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้дด็็็็็้้้้้็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้
-
View User Profile
-
View Posts
-
Send Message
Retired StaffYes, it is by that, that I have pulled the conclusion that he might not have the 64-bit version of Java. Just because he has 64bit Windows, it does not mean he has 64bit Java.
Yes, you can. You can install both x86 and x64 programs on a 64-bit machine.
The problem is clearly a memory leak issue. MC hasn't crashed as of yet, just becomes so laggy that it becomes unplayable and my system provides the out of memory warning. I am using Opti-Fine (latest for 1.5.1). I have reinstalled Java 7 with current update. No joy. I use magic launcher to swap between Jar files 1.4.7 and 1.5.1. I also use the magic launcher to set the memory for MC.
1.5.1 is an incredible memory hog. 1.4.7 has no such issue.
MC v1.5 - Win 7 SP1 64 bit - Intel I5 6970k - Gigabyte Z97X-UD5H-BK
16 Gigs Corsair Vengeance DDR3 - EVGA GTX 770 - Seagate SSD (240 Gig)
edit: I also completely uninstalled Java and installed it again. 64-bit
Java 64bit
Running latest forge & optifine.
It starts out with a FPS drop, but gradually it becomes so laggy, Its unplayable.
Although now that I think about it those my be in my big inaccessable void. My guess is that the world file is corrupt. Does anyone else having this issue have the big void area? (check my thread if you don't know what I'm talking about)
or according the windows memory management.
it will crash frequently.
i am using the linux.
i seldom crash that is cause by out of memory.
If you read the OP you'd know that he has already tried that (as did I)
And if you read the post above yours you'd know that I have already isolated the problem.