I could play for hours, until I got tired of pick axe'n blocks before the last patch.
Now after patching to 1.8.1 I cant play for more than 30 seconds.
Always get the message
"Minecraft has run out of memory,
This could be caused by a bug in the game or by the
Java Virtual Machine not being allocated enough
memory. If you are playing in a web browser, try
downloading the game and playing it offline.
To prevent level corruption, the current game has quit.
Please restart the game."
I'm using the exe, (ei not the browser).
Should I do anything else to try to get it to work normal or is this patch DOA for me :<
however one would hope that the minecraft application could check for you and.. avoid the issue :tongue.gif:
It's a dumbness shared by java and windows, I had the same issue too. Should fix it when you install 64bit java. If not, try the above recommendations. Many people play it fine, including me, so I don't think an update will specifically ruin the game for you performance-wise
The thing is, AFAIK, only 64bit OS could install 64bit java, which reported by others, fixed a lot of their issues. So is that to say only 64bit OS have this OUT OF MEMORY bug?
64 bit Windows 7 with 64 bit Java is running it fine. I'm also running 1.8 on Ubuntu 64bit 10.4 LTS with no crashes at all. In fact I've gotten better performance out of Minecraft on my Ubuntu partition then I have with Windows.
:sad.gif:
i have 32 bit windows vista ultimate (SHADDUP ABOUT WINDOWS VISTA) and it keeps happening i cant go to 64 bit java cus im 32 bit, it happend recently on reddit server and rarley on singleplayer but it happens alot on my dedicated server. its only happend after 1.8.1 why wont mojang fix! is there any other fix for a memory leak cause i cant live without minecraft XD
I've done a lot of research on this particular issue because I've had problems ever since the 1.6 update. What I'm about to list is just from personal experience with my own personal machines and may not apply to everyone. Hopefully this information will help narrow down the actual issue.
Things I've concluded:
1: Minecraft is *NOT* using all of your system RAM.
2: Java is *NOT* using all of your system RAM.
3: As long as you aren't running too many other programs, you *should* be able to run Minecraft perfectly fine with 2GB of RAM.
4: Microsoft Windows Vista 32-bit(TM) is a giant steaming turd.
5: XP seems to handle this problem better in general, although it may have other issues. (see: lag.)
6: Adjusting the Xmx and Xms sizes in 32-bit Vista (Java 1.7) rarely has any result either positive or negative.
7: This whole issue seems to be related to Java's garbage collection (or near lack thereof) and overrunning it's assigned max value. Problem is, we're not getting the debug information like we do with OpenGL errors, so it's hard to tell exactly at what point in the code this is happening.
So people have been having this problem before 1.73?
I know there are some reports about Out of memory problem, but is it as often as 1.8? Like every few minutes?
If so, then I can't blame 1.8... But I've been playing 1.73 perfectly fine until 1.8, even 1.8 PR 2 works better than 1.8, that doesn't make any sense... :sad.gif:
I honestly am not sure if I am using 32 bit or 64 bit Java on my 64 bit Win7 home Premium, But I have never gotten a crash like this so I guess it won't matter until I do.
Off topic: I liked Vista fine, never had a single problem with it.
Rollback Post to RevisionRollBack
Want some advice on how to thrive in the Suggestions section? Check this handy list of guidelines and tips for posting your ideas and responding to the ideas of others!
After updating Java to the newest version I was able to play for... almost four hours now (including times where I just left the window open and did other stuff). Damn I got lost in one of those generated mining shafts and finally just dug my way out a few minutes ago before closing Minecraft. So far it hasn't crashed again.
Tomorrow I'll probably try to play with a 16x16 texture pack. I'm curious if it will die on me again.
so youre 32 bit? and you updated to java 7? correct?
I've been having this problem since 1.3, I have fully updated Java, 4GB of RAM, a pretty good GFX card, my computer is actually a gaming computer, and I crash ever hour or so.
I've been told it's just a Java issue, and some computers will have this issue, and some won't, I find that some what true/un reliable, I've heard of people having exact same PC's, but one won't have this issue, and the other will.
Rollback Post to RevisionRollBack
War doesn't determine who's right, it determines who's left.
That's odd.
I was using Windiws 7 64bit and Java 32 bit.
Then 1.8.1 came out and I started to get all those "run out of memory" errors.
I read this thread, upgraded java to 64bit.
After that Minecraft won't even launch. Nothing happens after doubleclick.
Reinstalling doesn't help, no reaction
I uninstalled 64-java, got back to 32bit version and the game came is launching again, but after a minute or so it crashes with the known error.
It seems for me, there is a particular area of my world that doesnt crash. Well, it does, but it takes much much longer to do so. Maybe every half hour to an hour for it to crash. Luckily, this area is where my home is. Everywhere else, it crashes every 8-15 seconds.
I have plenty of RAM, im using current Java and video card drivers, so whats the deal? I have never had a problem with Minecraft before this 1.8 update. One of my computer knowledgeable friends says its a memory leak and I agree. My RAM usage keeps going up and up, never stopping until it just crashes.
Considering no one seems to have a solution that actually works for everybody, im going to label this problem a bug. I hope Mojang knows about it and is trying to fix it because any time I go out exploring or Mining for more resources, its nothing but frustration.
Remove all your texture packs and mods. I'm 100% sure that will fix it. I was having the same exact problem, I removed my texture packs, it fixed itself.
1.8 has a memory leak. Set your render distance to normal or shorter. If you press f3 with far distance on, you can actually see how the memory leak is causing the game to crash on the top right. Your memory usage slowly increases by time, then the game runs out and crashes. Normal distance has a pretty stable usage. I have never ran out on normal.
I could play for hours, until I got tired of pick axe'n blocks before the last patch.
Now after patching to 1.8.1 I cant play for more than 30 seconds.
Always get the message
"Minecraft has run out of memory,
This could be caused by a bug in the game or by the
Java Virtual Machine not being allocated enough
memory. If you are playing in a web browser, try
downloading the game and playing it offline.
To prevent level corruption, the current game has quit.
Please restart the game."
I'm using the exe, (ei not the browser).
Should I do anything else to try to get it to work normal or is this patch DOA for me :<
I will try this first, thankyou
however one would hope that the minecraft application could check for you and.. avoid the issue :tongue.gif:
It's a dumbness shared by java and windows, I had the same issue too. Should fix it when you install 64bit java. If not, try the above recommendations. Many people play it fine, including me, so I don't think an update will specifically ruin the game for you performance-wise
looks like that was the fix, thanks!
i have 32 bit windows vista ultimate (SHADDUP ABOUT WINDOWS VISTA) and it keeps happening i cant go to 64 bit java cus im 32 bit, it happend recently on reddit server and rarley on singleplayer but it happens alot on my dedicated server. its only happend after 1.8.1 why wont mojang fix! is there any other fix for a memory leak cause i cant live without minecraft XD
Things I've concluded:
1: Minecraft is *NOT* using all of your system RAM.
2: Java is *NOT* using all of your system RAM.
3: As long as you aren't running too many other programs, you *should* be able to run Minecraft perfectly fine with 2GB of RAM.
4: Microsoft Windows Vista 32-bit(TM) is a giant steaming turd.
5: XP seems to handle this problem better in general, although it may have other issues. (see: lag.)
6: Adjusting the Xmx and Xms sizes in 32-bit Vista (Java 1.7) rarely has any result either positive or negative.
7: This whole issue seems to be related to Java's garbage collection (or near lack thereof) and overrunning it's assigned max value. Problem is, we're not getting the debug information like we do with OpenGL errors, so it's hard to tell exactly at what point in the code this is happening.
I know there are some reports about Out of memory problem, but is it as often as 1.8? Like every few minutes?
If so, then I can't blame 1.8... But I've been playing 1.73 perfectly fine until 1.8, even 1.8 PR 2 works better than 1.8, that doesn't make any sense... :sad.gif:
Off topic: I liked Vista fine, never had a single problem with it.
Want some advice on how to thrive in the Suggestions section? Check this handy list of guidelines and tips for posting your ideas and responding to the ideas of others!
http://www.minecraftforum.net/forums/minecraft-discussion/suggestions/2775557-guidelines-for-the-suggestions-forum
so youre 32 bit? and you updated to java 7? correct?
I've been told it's just a Java issue, and some computers will have this issue, and some won't, I find that some what true/un reliable, I've heard of people having exact same PC's, but one won't have this issue, and the other will.
After HD Texture patch and HD Texture pack, the memory usage went up to 600M-800M and finally crashed after 20 mins.
Went to install Java 64bit, memory usage still high, but played for 40 mins, no crash yet... :blink.gif:
I still need more testing thou...
I was using Windiws 7 64bit and Java 32 bit.
Then 1.8.1 came out and I started to get all those "run out of memory" errors.
I read this thread, upgraded java to 64bit.
After that Minecraft won't even launch. Nothing happens after doubleclick.
Reinstalling doesn't help, no reaction
I uninstalled 64-java, got back to 32bit version and the game came is launching again, but after a minute or so it crashes with the known error.
Anyone knows what to do about it?
I have plenty of RAM, im using current Java and video card drivers, so whats the deal? I have never had a problem with Minecraft before this 1.8 update. One of my computer knowledgeable friends says its a memory leak and I agree. My RAM usage keeps going up and up, never stopping until it just crashes.
Considering no one seems to have a solution that actually works for everybody, im going to label this problem a bug. I hope Mojang knows about it and is trying to fix it because any time I go out exploring or Mining for more resources, its nothing but frustration.