Exception in server tick loop on InventoryHelper.getslots (not fixed by 0.2.13A)
ingrimmm opened this issue ยท 3 comments
Hi EBeef,
Wanted to report the following errors for you. We had this on SMP using v0.2.6A but it'd didn't go away even after upgrade to 0.2.13A.
This crashed the server and reboots wouldn't help.
We had to remove the mod, let the server delete the unknown blocks, and then put the mod back in.
Hope that means something - and thanks for the awesome mod.
---- Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.
Time: 1/3/14 10:56 PM
Description: Exception in server tick loop
java.lang.NullPointerException
at erogenousbeef.bigreactors.utils.InventoryHelper.getSlots(InventoryHelper.java:77)
at erogenousbeef.bigreactors.utils.InventoryHelper.addItem(InventoryHelper.java:36)
at erogenousbeef.bigreactors.common.tileentity.TileEntityReactorAccessPort.distributeItemToPipes(TileEntityReactorAccessPort.java:275)
at erogenousbeef.bigreactors.common.tileentity.TileEntityReactorAccessPort.onWasteReceived(TileEntityReactorAccessPort.java:287)
at erogenousbeef.bigreactors.common.multiblock.MultiblockReactor.tryDistributeWaste(MultiblockReactor.java:552)
at erogenousbeef.bigreactors.common.multiblock.MultiblockReactor.tryEjectWaste(MultiblockReactor.java:675)
at erogenousbeef.bigreactors.common.multiblock.MultiblockReactor.update(MultiblockReactor.java:244)
at erogenousbeef.core.multiblock.MultiblockControllerBase.updateMultiblockEntity(MultiblockControllerBase.java:571)
at erogenousbeef.core.multiblock.MultiblockRegistry.tick(MultiblockRegistry.java:38)
at erogenousbeef.core.multiblock.MultiblockServerTickHandler.tickStart(MultiblockServerTickHandler.java:25)
at cpw.mods.fml.common.SingleIntervalHandler.tickStart(SingleIntervalHandler.java:28)
at cpw.mods.fml.common.FMLCommonHandler.tickStart(FMLCommonHandler.java:122)
at cpw.mods.fml.common.FMLCommonHandler.onPreWorldTick(FMLCommonHandler.java:295)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:652)
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:276)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:587)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:484)
at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:583)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 1.6.4
Operating System: Linux (amd64) version 3.5.0-44-generic
Java Version: 1.7.0_45, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 90978848 bytes (86 MB) / 753401856 bytes (718 MB) up to 7478968320 bytes (7132 MB)
JVM Flags: 2 total; -XX:PermSize=1024m -Xmx8024M
AABB Pool Size: 6873 (384888 bytes; 0 MB) allocated, 359 (20104 bytes; 0 MB) used
Suspicious classes: FML and Forge are installed
IntCache: cache: 0, tcache: 30, allocated: 1, tallocated: 11
FML: MCP v8.11 FML v6.4.45.953 Minecraft Forge 9.11.1.953 155 mods loaded, 155 mods active
This is fixed in 0.2.13A2, and I added extra checks so even if you've hit some other weird edge case that I haven't imagined, it'll not crash but simply not output stuff into chests.
If, after this version, someone complains about an access port not ejecting waste into chests, please post a screenshot of their setup.