[MC 1.0.0] IC2 V 1.42: Bug, Nulear Reactor Crashes Both SSP and SMP When Cycle Completes

Aviendesora · December 20, 2011 at 5:43 AM

The subject says most of it but when any nuclear reactor i make on either SSP or SMP completes its cycle i get the following error (This is the error log from SSP, i don't have the one from SMP at the momment.)

Display Spoiler

java.lang.NullPointerException
at dk.a(SourceFile:181)
at ic2.common.TileEntityNuclearReactor.generateEnergy(TileEntityNuclearReactor.java:614)
at ic2.common.TileEntityNuclearReacter.processChamber(TileEntityNuclearReactor.java:488 )
at ic2.common.TileEntityNuclearReacter.processChamgers(TileEntityNuclearReactor.java:419)
at ic2.common.TileEntityNuclearReacter.b(TileEntityNuclearReactor.java:131)
at ry.m(World.java:1572)
at net.minecraft.client.Minecraft.k(SourceFile:1589)
at net.minecraft.client.Minecraft.x(SourceFile:705)
at net.minecraft.client.Minecraft.run(SourceFile:658 )
at java.lang.Thread.run(Unkown Source)

At this point the server crashes, though the server runs fine until the reactor is loaded in render distance. After someone logs near the reactor, they stay connected for a few seconds and this error happens. During this time connected the player is unable to interact with the world.

ShadwDrgn · December 20, 2011 at 5:58 AM

I just had this on my server.

Display Spoiler

java.lang.NullPointerException
at jb.a(SourceFile:181)
at ic2.common.TileEntityNuclearReactor.generateEnergy(TileEntityNuclearReactor.java:614)
at ic2.common.TileEntityNuclearReactor.processChamber(TileEntityNuclearReactor.java:488)
at ic2.common.TileEntityNuclearReactor.processChambers(TileEntityNuclearReactor.java:419)
at ic2.common.TileEntityNuclearReactor.l_(TileEntityNuclearReactor.java:131)
at fi.f(World.java:1204)
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:446)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:353)
at cu.run(SourceFile:457)
2011-12-20 00:46:15 [SEVERE] Unexpected exception
java.lang.NullPointerException
at jb.a(SourceFile:181)
at ic2.common.TileEntityNuclearReactor.generateEnergy(TileEntityNuclearReactor.java:614)
at ic2.common.TileEntityNuclearReactor.processChamber(TileEntityNuclearReactor.java:488)
at ic2.common.TileEntityNuclearReactor.processChambers(TileEntityNuclearReactor.java:419)
at ic2.common.TileEntityNuclearReactor.l_(TileEntityNuclearReactor.java:131)
at fi.f(World.java:1204)
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:446)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:353)
at cu.run(SourceFile:457)

Looks similar and server became unresponsive after.

Rick · December 20, 2011 at 7:07 AM

Damn thats a serious bug

Edit: just happened to me too....exacty at the moment the cycle ended.

ccrraazzyyman · December 20, 2011 at 9:02 AM

Mine just bit the dust too.

Happened right as a cycle was finishing (I watched it)

How do I attach the crash report? I don't know where it's located EDIT: Found it.

Display Spoiler

java.lang.NullPointerException
at dk.a(SourceFile:181)
at ic2.common.TileEntityNuclearReactor.generateEnergy(TileEntityNuclearReactor.java:614)
at ic2.common.TileEntityNuclearReactor.processChamber(TileEntityNuclearReactor.java:488 )
at ic2.common.TileEntityNuclearReactor.processChambers(TileEntityNuclearReactor.java:419)
at ic2.common.TileEntityNuclearReactor.b(TileEntityNuclearReactor.java:131)
at ry.m(World.java:1572)
at net.minecraft.client.Minecraft.k(SourceFile:1589)
at net.minecraft.client.Minecraft.x(SourceFile:705)
at net.minecraft.client.Minecraft.run(SourceFile:658 )
at java.lang.Thread.run(Unknown Source)

itburns · December 20, 2011 at 12:16 PM

I'm getting this error as well.

Display Spoiler

Mods loaded: 9
ModLoader 1.0.0
mod_ModLoaderMp 1.0.0
mod_BCIC2Crossover 1.01 for MC 1.0, BC 2.2.8, IC2 1.42
mod_BuildCraftCore 2.2.8
mod_BuildCraftBuilders 2.2.8
mod_BuildCraftEnergy 2.2.8
mod_BuildCraftFactory 2.2.8
mod_BuildCraftTransport 2.2.8
mod_IC2 v1.42

Minecraft has crashed!
----------------------

Minecraft has stopped running because it encountered a problem.

If you wish to report this, please copy this entire text and email it to support@mojang.com.
Please include a description of what you did when the error occured.

--- BEGIN ERROR REPORT 4c4b560a --------
Generated 12/20/11 7:03 AM

Minecraft: Minecraft 1.0.0
OS: Windows 7 (amd64) version 6.1
Java: 1.6.0_27, Sun Microsystems Inc.
VM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Sun Microsystems Inc.
LWJGL: 2.4.2
OpenGL: AMD Radeon HD 6900 Series version 4.1.11251 Compatibility Profile Context, ATI Technologies Inc.

java.lang.NullPointerException
at dk.a(SourceFile:181)
at ic2.common.TileEntityNuclearReactor.generateEnergy(TileEntityNuclearReactor.java:614)
at ic2.common.TileEntityNuclearReactor.processChamber(TileEntityNuclearReactor.java:488)
at ic2.common.TileEntityNuclearReactor.processChambers(TileEntityNuclearReactor.java:419)
at ic2.common.TileEntityNuclearReactor.b(TileEntityNuclearReactor.java:131)
at ry.m(World.java:1572)
at net.minecraft.client.Minecraft.k(SourceFile:1589)
at net.minecraft.client.Minecraft.x(SourceFile:705)
at net.minecraft.client.Minecraft.run(SourceFile:658)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT a5b59ee0 ----------

It has happened twice so far, both times in single-player survival. Upon attempting to reload the save I'm getting the "Saving Chunks"/Blackscreen type of crash. I've been able to load the map normally when I remove the reactors using a map edit.

alexthesax · December 20, 2011 at 1:38 PM Official Post

Alright, seems pretty serious, I'll see what I can do about this tonight. Hoping to get out some hotfix in the next day or two, we'll see how it goes.

itburns · December 20, 2011 at 3:03 PM

I should also note that this all happened with items generated using the Too Many Items mod.

HeadHunter67 · December 20, 2011 at 3:07 PM

Quote from itburns

I should also note that this all happened with items generated using the Too Many Items mod.

So, did you test it first with legitimately crafted items before adding your report? Because if it's just TMI items, that's not a bug in IC2. I don't know whether or not that's the case for the others, as they didn't mention it.

TMI isn't merely a casual eyewitness to many of these issues - it's the perpetrator. It's merely mistaken for an innocent bystander by people who are unaccustomed to being thorough (i.e., the mod's target audience).

Corvidae · December 20, 2011 at 3:32 PM

I can confirm this happening on stock 1.42, no other mods (including TMI), completely legit.

My crash dump happens as soon as the server starts and is in jb.a @ line 181 (as seen in ShadwDrgn's post), not dk.a like in the other posts.

Hopefully this helps.

MJEvans · December 20, 2011 at 5:52 PM

I'm guessing it's related to removing the uranium that are spent/the uranium damage counters reaching their 'zero' condition. However I don't know if that's some interaction with vanilla minecraft (like batpack + damage = no more batpack; but seems unlikely to share codepath, merely observed condition) or just a race condition within IC2.

starxplor · December 20, 2011 at 7:06 PM

My first reactor run with a single uranium cell worked fine. I had IC2 and treecapaciter mods only. The second run, 4 uranium cells, with BC2.2.8 added to the mix crashes on cycle completion.
It could also be an issue with replacing spent cells with depleted uranium cells, as a 4-cell reactor is more likely to create one than a one celled reactor.

Corvidae · December 20, 2011 at 7:12 PM

Good point, starx. I hadn't thought of that.

I was running a MkI reactor design (my first one ever, so I thought I'd play it safe) and had 2 cells in mine.

Here's the layout I was using, if it matters:

http://www.talonfiremage.pwp.blueyonder.co.uk/reactorplanner…001501521s1r11r

itburns · December 20, 2011 at 7:38 PM

Quote from HeadHunter67

So, did you test it first with legitimately crafted items before adding your report? Because if it's just TMI items, that's not a bug in IC2. I don't know whether or not that's the case for the others, as they didn't mention it.

TMI isn't merely a casual eyewitness to many of these issues - it's the perpetrator. It's merely mistaken for an innocent bystander by people who are unaccustomed to being thorough (i.e., the mod's target audience).

No, and that's why I specifically mentioned it. I don't believe that to be the case, especially after reading the other posts. Don't let that get in the way of your being smug.

HeadHunter67 · December 20, 2011 at 7:43 PM

Quote from itburns

Don't let that get in the way of your being smug.

What's "smug" got to do with it? I pointed out that others should check to see if it's a TMI-related issue.
If you doubt that it could possibly be the case, feel free to look around this forum (and the BC forum, and the MCF) and see how often TMI turns out to be the cause, rather than an accessory after the fact.
So the next step, of course, would be for you (and others who have reported the issue) to verify if it happens with crafted reactors as well.

This is a very serious issue, no doubt - so let's be sure of the cause, OK?

ShadwDrgn · December 20, 2011 at 7:46 PM

Quote from HeadHunter67

What's "smug" got to do with it? I pointed out that others should check to see if it's a TMI-related issue.
If you doubt that it could possibly be the case, feel free to look around this forum (and the BC forum, and the MCF) and see how often TMI turns out to be the cause, rather than an accessory after the fact.
So the next step, of course, would be for you (and others who have reported the issue) to verify if it happens with crafted reactors as well.

This is a very serious issue, no doubt - so let's be sure of the cause, OK?

As has already been pointed out. this is not TMI related. It's been tested legit. It was legit on my server, too.

HeadHunter67 · December 20, 2011 at 7:59 PM

Quote from ShadwDrgn

As has already been pointed out. this is not TMI related. It's been tested legit. It was legit on my server, too.

Yes, Corvidae mentioned it in a response after my initial post. My comment was not intended to be smug, but anyone who's got any experience with using mods ought to agree that when TMI is mentioned, one needs to eliminate that possiblity before anything else. Even Alblaka has stated that a couple of bugs that got into IC2 1.337 (like the CFpack issues) were due to testers using TMI items and declaring something "working".

Given everything I've read, I would not be surprised if it turns out to be related to cell depletion after all.

alexthesax · December 20, 2011 at 8:24 PM Official Post

Wouldn't surprise me either, I reworked the damaging code to avoid an NPE there, currently testing the reactor, within mins of finding out if everything goes well, if it doesn't I'll look into the code that makes a cell deplete. I'll keep you guys posted on updates.

alexthesax · December 20, 2011 at 8:51 PM Official Post

Well looks like after a few more changes, I've got a working version, thanks for the good error reports, they help so much

Expect this in the next version, Al will prob want some more testing on my fixes, but we'll get this out to you guys with the GUI id fix, and other misc stuff asap.

xKillerbees · December 20, 2011 at 9:02 PM Official Post

Thanks alex, long as it's by tomorrow for IR's update. I'm happy.

starxplor · December 21, 2011 at 7:18 AM

Quote from alexthesax

Well looks like after a few more changes, I've got a working version, thanks for the good error reports, they help so much

Expect this in the next version, Al will prob want some more testing on my fixes, but we'll get this out to you guys with the GUI id fix, and other misc stuff asap.

Thanks for the quick response.

P.S. I meant treecapitator, but treecapacitor does sound like fun, trees storing EU and all...

Users Viewing This Thread