Having an issue on my modded profile where the game will abruptly stop responding. I'll then be greeted with a "Shutting down internal server" message that hangs indefinitely (and makes my computer's fans really upset). This issue can either happen when I'm trying to access the interface of a mod block, typically one I've not used yet in the play through, but occasionally happens literally doing nothing. The game begins to spike periodically, and then permanently - then the "internal server" shuts down.
Even more frustrating, the game seemingly outputs absolutely no crash log or error. The game log simply says "Shutting down!" on the last line. Nothing is generated in the crash-report folder via Forge. Nothing is generated to the OS X console. Minecraft never actually even closes until I force it to, it just hangs forever on "Shutting down internal server."
I have quite a few mods installed:
Applied Energistics 2
Archimedes Ships
Big Reactors
Chisel 2
Thermal Foundation, Expansion, Dynamics
Ender IO
Extra Utilities
Tinker's Construct
CoFH Core (dependency of Thermal Expansion)
Mantle (dependency of Tinkers' Construct)
And... finally, NotEnoughItems
NotEnoughItems is the culprit. I don't know why, and I don't know how, but when I remove NotEnoughItems and its dependency, CodeChickenCore (I suppose I could try to regression-test CodeChickenCore by itself or with a different CodeChicken mod, like Ender Storage), from my mods folder, the game runs just fine. Period. I've tried installing numerous different versions of NotEnoughItems and its core. Usually installing other versions results in hard-crashing the moment I open my inventory. The "Most" stable combination I've used - and the combination that is causing the erratic freezing - is NEI 1.0.3.74 with CCC 1.0.4.29.
I have NO idea what is going on.
Can't get a crash report. There's literally nothing being generated anywhere.
Minecraft never actually closes. It just hangs on "Shutting down internal server" forever. No crash message.
Forge does not output a crash message to the crash-reports directory.
The log simply reports "Shutting down!" on the last line.
The OS X console does not output anything relevant to Minecraft, or even anything timestamped at the time of the game shutting down.
This most recent "crash," I did actually get a little more in the Game Output window (only after forcibly quitting the client). The line prior to "Stopping Server" was timestamped 15 minutes prior, so in theory the following is the only relevant information I have...
[16:26:58] [Server thread/INFO]: Stopping server<br>[16:26:58] [Server thread/INFO]: Saving players<br>[16:26:58] [Server thread/INFO]: Saving worlds<br>[16:26:59] [Server thread/INFO]: Saving chunks for level '20Mod World'/Overworld<br>Exception in thread "Netty IO #5" [16:27:08] [Server thread/INFO]: Saving chunks for level '20Mod World'/Nether<br>[16:27:08] [Server thread/INFO]: Saving chunks for level '20Mod World'/The End<br>[16:27:08] [Server thread/INFO]: Saving chunks for level '20Mod World'/Underdark<br>[16:27:08] [Server thread/INFO]: Saving chunks for level '20Mod World'/The Last Millenium<br>[16:27:12] [Server thread/INFO] [FML]: Applying holder lookups<br>[16:27:12] [Server thread/WARN] [FML]: Unable to lookup chisel:cobblestoneWall for public static com.cricketcraft.chisel.block.BlockMarbleWall com.cricketcraft.chisel.init.ChiselBlocks.cobblestoneWall. Is there something wrong with the registry?<br>[16:27:12] [Server thread/WARN] [FML]: Unable to lookup chisel:obsidian2 for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.obsidian2. Is there something wrong with the registry?<br>[16:27:12] [Server thread/WARN] [FML]: Unable to lookup chisel:arcane for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.arcane. Is there something wrong with the registry?<br>[16:27:12] [Server thread/WARN] [FML]: Unable to lookup chisel:thaumium for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.thaumium. Is there something wrong with the registry?<br>[16:27:12] [Server thread/WARN] [FML]: Unable to lookup chisel:tallow for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.tallow. Is there something wrong with the registry?<br>[16:27:12] [Server thread/WARN] [FML]: Unable to lookup chisel:bloodRune for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.bloodRune. Is there something wrong with the registry?<br>[16:27:12] [Server thread/WARN] [FML]: Unable to lookup chisel:bloodBrick for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.bloodBrick. Is there something wrong with the registry?<br>[16:27:12] [Server thread/INFO] [FML]: Holder lookups applied<br>[16:27:12] [pool-4-thread-1/INFO] [EnderIO]: ServerChannelRegister: Dimensional Trasciever data saved to /Users/[USERNAME]/Library/Application Support/minecraft/saves/20Mod World/enderio/dimensionalTransceiver.json<br>Exception in thread "Server thread" Exception in thread "Snooper Timer" Exception in thread "Snooper Timer" 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
I suppose it would be silly to ask "Has anyone had this problem?" since I'm using a very specific non-mod-pack organization of mods, but perhaps someone has an idea as to why this might be happening?
Well I've never had that kind of problem with NEI but it can be intensive on some packs. It probably wont fix you'r problem but try adding Fast Craft and FPS Plus to boost your frame rate and decrease chances of freezing. Also Mantel is required for Tinkers Construct.
Rollback Post to RevisionRollBack
When angry, count to four; when very angry, swear. Samuel Langhorne Clemens
I'm sorry, I should clarify - the game doesn't stutter and freeze because it's frameskipping. I mean the game stops responding, and shuts itself down.
I'm going to attempt to glean a crash report, but it's not easy. Forge isn't saving a crash report to the crash-reports directory and Minecraft doesn't output a report when the game shuts down.
Can't get a crash report. There's literally nothing being generated anywhere.
Minecraft never actually closes. It just hangs on "Shutting down internal server" forever. No crash message.
Forge does not output a crash message to the crash-reports directory.
The log simply reports "Shutting down!" on the last line.
The OS X console does not output anything relevant to Minecraft, or even anything timestamped at the time of the game shutting down.
EDIT:
Actually, I do get ONE thing in the game output, after forcibly quitting the Minecraft Client:
Exception in thread "Server thread" Exception in thread "Snooper Timer" Exception in thread "Snooper Timer" 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
Welp. I'm a big ole' idiot. Here I am sitting on 16gb of RAM and I forgot to tell Minecraft it could use more... somehow. I feel like I did this a long time ago.
Guess things never change.
Thanks grimallq, even if you pointed out the obvious. I totally saw that in the log, too, and dismissed it as unimportant (I am gud at computer, guys).
Anyhow, I'll poke my profile java arguments and test it some more, see if it buggers off.
So, I went into my modded profile and set the JVM argument -Xmx4G up from 1G. Played for a while, seemed like things were going more smoothly... until I crashed again. I was monitoring the application's RAM usage the entire time, and it never exceeded 1.06gb. However, Game Output gave me java.lang.OutOfMemoryError again...
This time, it was accessing the console of a big reactor (which I'd built previously and had used before, so so much for the "interfaces of modded blocks I'd not used before" rule). Game spiked for several seconds. I got a single additional frame, and then I was back to the never-ending "Shutting down internal server" screen.
Game output at time of crash:
Exception in thread "Thread-18" [18:05:27] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2280ms behind, skipping 45 tick(s) [18:05:33] [Server thread/INFO]: Stopping server [18:05:35] [Server thread/INFO] [FML]: Applying holder lookups [18:05:35] [Server thread/WARN] [FML]: Unable to lookup chisel:cobblestoneWall for public static com.cricketcraft.chisel.block.BlockMarbleWall com.cricketcraft.chisel.init.ChiselBlocks.cobblestoneWall. Is there something wrong with the registry? [18:05:35] [Server thread/WARN] [FML]: Unable to lookup chisel:obsidian2 for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.obsidian2. Is there something wrong with the registry? [18:05:35] [Server thread/WARN] [FML]: Unable to lookup chisel:arcane for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.arcane. Is there something wrong with the registry? [18:05:35] [Server thread/WARN] [FML]: Unable to lookup chisel:thaumium for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.thaumium. Is there something wrong with the registry? [18:05:35] [Server thread/WARN] [FML]: Unable to lookup chisel:tallow for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.tallow. Is there something wrong with the registry? [18:05:35] [Server thread/WARN] [FML]: Unable to lookup chisel:bloodRune for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.bloodRune. Is there something wrong with the registry? [18:05:35] [Server thread/WARN] [FML]: Unable to lookup chisel:bloodBrick for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.bloodBrick. Is there something wrong with the registry? [18:05:35] [Server thread/INFO] [FML]: Holder lookups applied Exception in thread "Server thread" 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
Launcher Log at time of crash:
[18:06:00 ERROR]: Game ended with bad state (exit code 137) [18:06:00 INFO]: Ignoring visibility rule and showing launcher due to a game crash [18:06:00 INFO]: Deleting /Users/[USERNAME]/Library/Application Support/minecraft/versions/1.7.10-Forge10.13.2.1291/1.7.10-Forge10.13.2.1291-natives-1428963707353191000
FML client log:
[18:05:05] [Server thread/DEBUG] [FML/]: Gathering id map for writing to world save 20Mod World<br>[18:05:33] [Server thread/TRACE] [mcp/mcp]: Sending event FMLServerStoppingEvent to mod mcp<br>[18:05:33] [Server thread/TRACE] [mcp/mcp]: Sent event FMLServerStoppingEvent to mod mcp<br>[18:05:33] [Server thread/TRACE] [FML/FML]: Sending event FMLServerStoppingEvent to mod FML<br>[18:05:33] [Server thread/TRACE] [FML/FML]: Sent event FMLServerStoppingEvent to mod FML<br>[18:05:33] [Server thread/TRACE] [Forge/Forge]: Sending event FMLServerStoppingEvent to mod Forge<br>[18:05:33] [Server thread/TRACE] [Forge/Forge]: Sent event FMLServerStoppingEvent to mod Forge<br>[18:05:33] [Server thread/TRACE] [appliedenergistics2-core/appliedenergistics2-core]: Sending event FMLServerStoppingEvent to mod appliedenergistics2-core<br>[18:05:33] [Server thread/TRACE] [appliedenergistics2-core/appliedenergistics2-core]: Sent event FMLServerStoppingEvent to mod appliedenergistics2-core<br>[18:05:33] [Server thread/TRACE] [CodeChickenCore/CodeChickenCore]: Sending event FMLServerStoppingEvent to mod CodeChickenCore<br>[18:05:33] [Server thread/TRACE] [CodeChickenCore/CodeChickenCore]: Sent event FMLServerStoppingEvent to mod CodeChickenCore<br>[18:05:33] [Server thread/TRACE] [NotEnoughItems/NotEnoughItems]: Sending event FMLServerStoppingEvent to mod NotEnoughItems<br>[18:05:33] [Server thread/TRACE] [NotEnoughItems/NotEnoughItems]: Sent event FMLServerStoppingEvent to mod NotEnoughItems<br>[18:05:33] [Server thread/TRACE] [<CoFH ASM>/<CoFH ASM>]: Sending event FMLServerStoppingEvent to mod <CoFH ASM><br>[18:05:33] [Server thread/TRACE] [<CoFH ASM>/<CoFH ASM>]: Sent event FMLServerStoppingEvent to mod <CoFH ASM><br>[18:05:33] [Server thread/TRACE] [appliedenergistics2/appliedenergistics2]: Sending event FMLServerStoppingEvent to mod appliedenergistics2<br>[18:05:33] [Server thread/TRACE] [appliedenergistics2/appliedenergistics2]: Sent event FMLServerStoppingEvent to mod appliedenergistics2<br>[18:05:33] [Server thread/TRACE] [ArchimedesShips/ArchimedesShips]: Sending event FMLServerStoppingEvent to mod ArchimedesShips<br>[18:05:33] [Server thread/TRACE] [ArchimedesShips/ArchimedesShips]: Sent event FMLServerStoppingEvent to mod ArchimedesShips<br>[18:05:33] [Server thread/TRACE] [CoFHCore/CoFHCore]: Sending event FMLServerStoppingEvent to mod CoFHCore<br>[18:05:33] [Server thread/TRACE] [CoFHCore/CoFHCore]: Sent event FMLServerStoppingEvent to mod CoFHCore<br>[18:05:33] [Server thread/TRACE] [ThermalFoundation/ThermalFoundation]: Sending event FMLServerStoppingEvent to mod ThermalFoundation<br>[18:05:33] [Server thread/TRACE] [ThermalFoundation/ThermalFoundation]: Sent event FMLServerStoppingEvent to mod ThermalFoundation<br>[18:05:33] [Server thread/TRACE] [ThermalExpansion/ThermalExpansion]: Sending event FMLServerStoppingEvent to mod ThermalExpansion<br>[18:05:33] [Server thread/TRACE] [ThermalExpansion/ThermalExpansion]: Sent event FMLServerStoppingEvent to mod ThermalExpansion<br>[18:05:33] [Server thread/TRACE] [BigReactors/BigReactors]: Sending event FMLServerStoppingEvent to mod BigReactors<br>[18:05:33] [Server thread/TRACE] [BigReactors/BigReactors]: Sent event FMLServerStoppingEvent to mod BigReactors<br>[18:05:33] [Server thread/TRACE] [chisel/chisel]: Sending event FMLServerStoppingEvent to mod chisel<br>[18:05:33] [Server thread/TRACE] [chisel/chisel]: Sent event FMLServerStoppingEvent to mod chisel<br>[18:05:33] [Server thread/TRACE] [EnderIO/EnderIO]: Sending event FMLServerStoppingEvent to mod EnderIO<br>[18:05:33] [Server thread/TRACE] [EnderIO/EnderIO]: Sent event FMLServerStoppingEvent to mod EnderIO<br>[18:05:33] [Server thread/TRACE] [ExtraUtilities/ExtraUtilities]: Sending event FMLServerStoppingEvent to mod ExtraUtilities<br>[18:05:33] [Server thread/TRACE] [ExtraUtilities/ExtraUtilities]: Sent event FMLServerStoppingEvent to mod ExtraUtilities<br>[18:05:33] [Server thread/TRACE] [Mantle/Mantle]: Sending event FMLServerStoppingEvent to mod Mantle<br>[18:05:33] [Server thread/TRACE] [Mantle/Mantle]: Sent event FMLServerStoppingEvent to mod Mantle<br>[18:05:33] [Server thread/TRACE] [TConstruct/TConstruct]: Sending event FMLServerStoppingEvent to mod TConstruct<br>[18:05:33] [Server thread/TRACE] [TConstruct/TConstruct]: Sent event FMLServerStoppingEvent to mod TConstruct<br>[18:05:33] [Server thread/TRACE] [ThermalDynamics/ThermalDynamics]: Sending event FMLServerStoppingEvent to mod ThermalDynamics<br>[18:05:33] [Server thread/TRACE] [ThermalDynamics/ThermalDynamics]: Sent event FMLServerStoppingEvent to mod ThermalDynamics<br>[18:05:35] [Server thread/DEBUG] [FML/]: Reverting to frozen data state.<br>[18:05:35] [Server thread/INFO] [FML/]: Applying holder lookups<br>[18:05:35] [Server thread/WARN] [FML/]: Unable to lookup chisel:cobblestoneWall for public static com.cricketcraft.chisel.block.BlockMarbleWall com.cricketcraft.chisel.init.ChiselBlocks.cobblestoneWall. Is there something wrong with the registry?<br>[18:05:35] [Server thread/WARN] [FML/]: Unable to lookup chisel:obsidian2 for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.obsidian2. Is there something wrong with the registry?<br>[18:05:35] [Server thread/WARN] [FML/]: Unable to lookup chisel:arcane for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.arcane. Is there something wrong with the registry?<br>[18:05:35] [Server thread/WARN] [FML/]: Unable to lookup chisel:thaumium for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.thaumium. Is there something wrong with the registry?<br>[18:05:35] [Server thread/WARN] [FML/]: Unable to lookup chisel:tallow for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.tallow. Is there something wrong with the registry?<br>[18:05:35] [Server thread/WARN] [FML/]: Unable to lookup chisel:bloodRune for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.bloodRune. Is there something wrong with the registry?<br>[18:05:35] [Server thread/WARN] [FML/]: Unable to lookup chisel:bloodBrick for public static com.cricketcraft.chisel.block.BlockCarvable com.cricketcraft.chisel.init.ChiselBlocks.bloodBrick. Is there something wrong with the registry?<br>[18:05:35] [Server thread/INFO] [FML/]: Holder lookups applied
Interesting that less than half a minute before the crash, the FML client log mentions "Gathering id map for writing to world save [save_name]"
I have the exact same issue, i created a modpack and it runs smoothly, but overtime I add Open Blocks, or any mod what so ever, it goes into "Shutting down internal sever" and have to Forcibly terminate. Help?
Having an issue on my modded profile where the game will abruptly stop responding. I'll then be greeted with a "Shutting down internal server" message that hangs indefinitely (and makes my computer's fans really upset). This issue can either happen when I'm trying to access the interface of a mod block, typically one I've not used yet in the play through, but occasionally happens literally doing nothing. The game begins to spike periodically, and then permanently - then the "internal server" shuts down.
Even more frustrating, the game seemingly outputs absolutely no crash log or error. The game log simply says "Shutting down!" on the last line. Nothing is generated in the crash-report folder via Forge. Nothing is generated to the OS X console. Minecraft never actually even closes until I force it to, it just hangs forever on "Shutting down internal server."
I have quite a few mods installed:
Applied Energistics 2
Archimedes Ships
Big Reactors
Chisel 2
Thermal Foundation, Expansion, Dynamics
Ender IO
Extra Utilities
Tinker's Construct
CoFH Core (dependency of Thermal Expansion)
Mantle (dependency of Tinkers' Construct)
And... finally, NotEnoughItems
NotEnoughItems is the culprit. I don't know why, and I don't know how, but when I remove NotEnoughItems and its dependency, CodeChickenCore (I suppose I could try to regression-test CodeChickenCore by itself or with a different CodeChicken mod, like Ender Storage), from my mods folder, the game runs just fine. Period. I've tried installing numerous different versions of NotEnoughItems and its core. Usually installing other versions results in hard-crashing the moment I open my inventory. The "Most" stable combination I've used - and the combination that is causing the erratic freezing - is NEI 1.0.3.74 with CCC 1.0.4.29.
I have NO idea what is going on.
Can't get a crash report. There's literally nothing being generated anywhere.
Minecraft never actually closes. It just hangs on "Shutting down internal server" forever. No crash message.
Forge does not output a crash message to the crash-reports directory.
The log simply reports "Shutting down!" on the last line.
The OS X console does not output anything relevant to Minecraft, or even anything timestamped at the time of the game shutting down.
This most recent "crash," I did actually get a little more in the Game Output window (only after forcibly quitting the client). The line prior to "Stopping Server" was timestamped 15 minutes prior, so in theory the following is the only relevant information I have...
I suppose it would be silly to ask "Has anyone had this problem?" since I'm using a very specific non-mod-pack organization of mods, but perhaps someone has an idea as to why this might be happening?
Well I've never had that kind of problem with NEI but it can be intensive on some packs. It probably wont fix you'r problem but try adding Fast Craft and FPS Plus to boost your frame rate and decrease chances of freezing. Also Mantel is required for Tinkers Construct.
When angry, count to four; when very angry, swear. Samuel Langhorne Clemens
I'm sorry, I should clarify - the game doesn't stutter and freeze because it's frameskipping. I mean the game stops responding, and shuts itself down.
I'm going to attempt to glean a crash report, but it's not easy. Forge isn't saving a crash report to the crash-reports directory and Minecraft doesn't output a report when the game shuts down.
Can't get a crash report. There's literally nothing being generated anywhere.
Minecraft never actually closes. It just hangs on "Shutting down internal server" forever. No crash message.
Forge does not output a crash message to the crash-reports directory.
The log simply reports "Shutting down!" on the last line.
The OS X console does not output anything relevant to Minecraft, or even anything timestamped at the time of the game shutting down.
EDIT:
Actually, I do get ONE thing in the game output, after forcibly quitting the Minecraft Client:
Welp. I'm a big ole' idiot. Here I am sitting on 16gb of RAM and I forgot to tell Minecraft it could use more... somehow. I feel like I did this a long time ago.
Guess things never change.
Thanks grimallq, even if you pointed out the obvious. I totally saw that in the log, too, and dismissed it as unimportant (I am gud at computer, guys).
Anyhow, I'll poke my profile java arguments and test it some more, see if it buggers off.
Sigh. Just couldn't be that simple, could it?
So, I went into my modded profile and set the JVM argument -Xmx4G up from 1G. Played for a while, seemed like things were going more smoothly... until I crashed again. I was monitoring the application's RAM usage the entire time, and it never exceeded 1.06gb. However, Game Output gave me java.lang.OutOfMemoryError again...
This time, it was accessing the console of a big reactor (which I'd built previously and had used before, so so much for the "interfaces of modded blocks I'd not used before" rule). Game spiked for several seconds. I got a single additional frame, and then I was back to the never-ending "Shutting down internal server" screen.
Game output at time of crash:
Launcher Log at time of crash:
FML client log:
Interesting that less than half a minute before the crash, the FML client log mentions "Gathering id map for writing to world save [save_name]"
I have the exact same issue, i created a modpack and it runs smoothly, but overtime I add Open Blocks, or any mod what so ever, it goes into "Shutting down internal sever" and have to Forcibly terminate. Help?
Has this been solved yet? I have the same issue. Minecraft isn't reading more than 1.36 GB of memory... I have allocated 6 GB.
Join this cool Datapack Discord server! https://discord.gg/XQg5wNt