I can start playing a world for 5-10 minutes, then I will get a lag spike every now and then. The screen will freeze, then go back to normal. The console is NOT outputting any errors. However, after only a few of these, the screen will freeze completely, and will shortly go to 'shutting down internal server'. It never actually shows the 'minecraft has crashed' screen though. I can see my CPU meter at 100% but only on one core. (I have a quad core macbook pro) I finally have to force minecraft to quit, as it will not stop on its own. I am still not getting any errors in the MultiMC console. There is only one thing that appears that doesn't look normal.
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal Unknown Signal to handler- the VM may need to be forcibly terminated
That's it. Everything else is normal. It does not have any names of any of my mods listed as warnings before that, so I have absolutely no idea what's causing it. It's getting REALLY annoying. Please help.
After a long time of waiting for no one to help, I FINALLY found a solution from someone that knew what the problem was after reporting a similar crash on another thread. Here is the solution:
It's not the RAM that is the problem, it's the 'permGen space'. It holds compiled code, instead of things it's working on. Like the instructions instead of the project being built. There are so many mods installed that it runs out of space for instructions. Allocating more memory will only give it more space for the project, not the instructions. To fix it, you need to add the following argument to the launch command for minecraft: -XX:MaxPermSize=256m
Unfortunately, I only know how to do this with MultiMC. I do not know how to do this on the standard version of Minecraft downloaded from minecraft.net. But if you do have MultiMC, you can do the following:
Click on the settings button, then go to the java tab, and look where it says JVM Arguments, then add -XX:MaxPermSize=256m to the box. 256 megabytes should be enough for a lot of code. I have about 80 mods, and have not had this problem ever sense I changed this setting. However, if you have over 9000 mods, you might need to up this number again.
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal Unknown Signal to handler- the VM may need to be forcibly terminated
-snip-
You need to dedicate more memory to minecraft. You have so much installed, it needs a helluva lot more memory to run.
Rollback Post to RevisionRollBack
MineZ Professional (On the Leaderboards: DuskShadowBrony) | Obsidian Shotbow Subscriber | Sucks at PvP
When I doubled my memory allocation, it was 1024 MB (1 GB) and now it's 2048 MB (2GB). I only have 4 GB of RAM, so I can't really increase it any more. In the activity monitor, I can see that MC uses about 1.5 GB on average. The problem is still here. I watched it with both windows next to each other so that I could see exactly how much memory MC was using when it lags out. It was a constant 1.5 GB. It doesn't use more memory during the lag spikes. It does, however, completely use one of my CPU cores as mentioned earlier. I also found a bit more information through the log file.
2013-02-14 17:43:28 [SEVERE] [ForgeModLoader] Detected leaking worlds in memory. There are 8 worlds that appear to be persisting. A mod is likely caching the world incorrectly
2013-02-14 17:43:28 [SEVERE] [ForgeModLoader] The world 27c1e949 (Tester) has leaked.
2013-02-14 17:43:28 [SEVERE] [ForgeModLoader] The world b5be8ff (Tester) has leaked.
2013-02-14 17:43:28 [SEVERE] [ForgeModLoader] The world 72d53513 (Tester) has leaked.
2013-02-14 17:43:28 [SEVERE] [ForgeModLoader] The world 635b2c1 (Tester) has leaked.
This message showed up about 45 minutes before the crash. That was about when the very first lag spike showed up. First one, then maybe 15 minutes layer, another one, and later a third, increasing in frequency the longer it goes on. About 1 minute before the crash, they occur about once every 5 seconds. Then the last one will start shutting down the internal server, and will not stop. Still using 100% of my CPU, and unable to get my mouse back yet, I have to force MC to quit using ⌘⌥⎋.
If anyone has any idea what's causing this, please help.
Having same issue with latest minecraft ftb pack (mc 1.4.7, mindcrack 7 pack). Lag spikes with increasing frequency then lock-up on "shutting down internal server".
I removed a couple of mods that I don't use, and the problem seems to be gone. I don't know which mod was causing it, and I still want to know how to fix it if it shows up again.
I am running into this exact same problem. Strange, considering I have 16 GB allocated to Minecraft...
Rollback Post to RevisionRollBack
There are no extra pieces in the universe. Everyone is here because he or she has a place to fill, and every piece must fit itself into the big jigsaw puzzle.
-Deepak Chopra
It's not the RAM that is the problem, it's the 'permGen space'. It holds compiled code, instead of things it's working on. Like the instructions instead of the project being built. There are so many mods installed that it runs out of space for instructions. Allocating more memory will only give it more space for the project, not the instructions. To fix it, you need to add the following argument to the launch command for minecraft: -XX:MaxPermSize=256m
Unfortunately, I only know how to do this with MultiMC. I do not know how to do this on the standard version of Minecraft downloaded from minecraft.net. But if you do have MultiMC, you can do the following:
Click on the settings button, then go to the java tab, and look where it says JVM Arguments, then add -XX:MaxPermSize=256m to the box. 256 megabytes should be enough for a lot of code. I have about 80 mods, and have not had this problem ever sense I changed this setting. However, if you have over 9000 mods, you might need to up this number again.
There are no extra pieces in the universe. Everyone is here because he or she has a place to fill, and every piece must fit itself into the big jigsaw puzzle.
-Deepak Chopra
It's not the RAM that is the problem, it's the 'permGen space'. It holds compiled code, instead of things it's working on. Like the instructions instead of the project being built. There are so many mods installed that it runs out of space for instructions. Allocating more memory will only give it more space for the project, not the instructions. To fix it, you need to add the following argument to the launch command for minecraft: -XX:MaxPermSize=256m
Unfortunately, I only know how to do this with MultiMC. I do not know how to do this on the standard version of Minecraft downloaded from minecraft.net. But if you do have MultiMC, you can do the following:
Click on the settings button, then go to the java tab, and look where it says JVM Arguments, then add -XX:MaxPermSize=256m to the box. 256 megabytes should be enough for a lot of code. I have about 80 mods, and have not had this problem ever sense I changed this setting. However, if you have over 9000 mods, you might need to up this number again.
That's it. Everything else is normal. It does not have any names of any of my mods listed as warnings before that, so I have absolutely no idea what's causing it. It's getting REALLY annoying. Please help.
After a long time of waiting for no one to help, I FINALLY found a solution from someone that knew what the problem was after reporting a similar crash on another thread. Here is the solution:
It's not the RAM that is the problem, it's the 'permGen space'. It holds compiled code, instead of things it's working on. Like the instructions instead of the project being built. There are so many mods installed that it runs out of space for instructions. Allocating more memory will only give it more space for the project, not the instructions. To fix it, you need to add the following argument to the launch command for minecraft: -XX:MaxPermSize=256m
Unfortunately, I only know how to do this with MultiMC. I do not know how to do this on the standard version of Minecraft downloaded from minecraft.net. But if you do have MultiMC, you can do the following:
Click on the settings button, then go to the java tab, and look where it says JVM Arguments, then add -XX:MaxPermSize=256m to the box. 256 megabytes should be enough for a lot of code. I have about 80 mods, and have not had this problem ever sense I changed this setting. However, if you have over 9000 mods, you might need to up this number again.
I made my own shader pack, by the way.
You need to dedicate more memory to minecraft. You have so much installed, it needs a helluva lot more memory to run.
MineZ Professional (On the Leaderboards: DuskShadowBrony) | Obsidian Shotbow Subscriber | Sucks at PvP
I made my own shader pack, by the way.
When I doubled my memory allocation, it was 1024 MB (1 GB) and now it's 2048 MB (2GB). I only have 4 GB of RAM, so I can't really increase it any more. In the activity monitor, I can see that MC uses about 1.5 GB on average. The problem is still here. I watched it with both windows next to each other so that I could see exactly how much memory MC was using when it lags out. It was a constant 1.5 GB. It doesn't use more memory during the lag spikes. It does, however, completely use one of my CPU cores as mentioned earlier. I also found a bit more information through the log file.
This message showed up about 45 minutes before the crash. That was about when the very first lag spike showed up. First one, then maybe 15 minutes layer, another one, and later a third, increasing in frequency the longer it goes on. About 1 minute before the crash, they occur about once every 5 seconds. Then the last one will start shutting down the internal server, and will not stop. Still using 100% of my CPU, and unable to get my mouse back yet, I have to force MC to quit using ⌘⌥⎋.
If anyone has any idea what's causing this, please help.
I made my own shader pack, by the way.
I made my own shader pack, by the way.
I made my own shader pack, by the way.
I made my own shader pack, by the way.
I made my own shader pack, by the way.
I made my own shader pack, by the way.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThere are no extra pieces in the universe. Everyone is here because he or she has a place to fill, and every piece must fit itself into the big jigsaw puzzle.
-Deepak Chopra
I made my own shader pack, by the way.
It's not the RAM that is the problem, it's the 'permGen space'. It holds compiled code, instead of things it's working on. Like the instructions instead of the project being built. There are so many mods installed that it runs out of space for instructions. Allocating more memory will only give it more space for the project, not the instructions. To fix it, you need to add the following argument to the launch command for minecraft: -XX:MaxPermSize=256m
Unfortunately, I only know how to do this with MultiMC. I do not know how to do this on the standard version of Minecraft downloaded from minecraft.net. But if you do have MultiMC, you can do the following:
Click on the settings button, then go to the java tab, and look where it says JVM Arguments, then add -XX:MaxPermSize=256m to the box. 256 megabytes should be enough for a lot of code. I have about 80 mods, and have not had this problem ever sense I changed this setting. However, if you have over 9000 mods, you might need to up this number again.
I made my own shader pack, by the way.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThere are no extra pieces in the universe. Everyone is here because he or she has a place to fill, and every piece must fit itself into the big jigsaw puzzle.
-Deepak Chopra
Thank you! Spread the word everyone!
I have 216 mods (only 15 big ones EG: ic2 buildcraft etc.) running on my server, how much should I allocate?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis post is 2 years old... PermGen was removed in java 8 so to answer your question - you shouldn't