StackOverflow Crash
Keridos opened this issue ยท 10 comments
Having this Crash with TC 4.2.3.5 and thaumicenergistics-0.8.9.0b-rv2: https://paste.ee/p/QeTR9
Sorry it took me so long to get around to this. I just tested with the latest version of Gregtech and had no problems. Are you still encountering issues?
Dunno, do not have GT in my pack anymore. But I think I asked Azanor to take a look at that and the GT guys, maybe one of them fixed this.
It's bug from Witching Gadgets, reported here:
BluSunrize/WitchingGadgets#13
From the crash log I can't rule out that my mod is causing some kind of issue, but the loop is getting stuck on these four lines:
"at thaumcraft.common.lib.crafting.ThaumcraftCraftingManager.generateTagsFromCrucibleRecipes(ThaumcraftCraftingManager.java:567)
at thaumcraft.common.lib.crafting.ThaumcraftCraftingManager.generateTagsFromRecipes(ThaumcraftCraftingManager.java:891)
at thaumcraft.common.lib.crafting.ThaumcraftCraftingManager.generateTags(ThaumcraftCraftingManager.java:551)
at thaumcraft.common.lib.crafting.ThaumcraftCraftingManager.generateTags(ThaumcraftCraftingManager.java:525)"
With the calling routine being:
"at thaumcraft.api.aspects.AspectList.copy(AspectList.java:35)"
So from just the report, it doesn't look like my code is involved. But more testing is required.
I have the same crash, but at different places.
Here is my log: http://paste.ee/p/aiI34
And here is the crash report: http://paste.ee/p/mUeDu
I have tried upgrading Mekanism, downgrading thaumcraft (plus all it's addons), and nothing I do makes it work. This crash, I believe, is your mod's doing and not thaumcraft's.
Tommy, that error is due an API mismatch between AE and Mekanism, and my code calling on invalid recipes within AE due to that issue.
See #147 for details.
On my instance I pretty much kicked out all TC mods except thaumic energistic but this still happens...
Thank you for that, I guess I missed that issue. I just decided to turn off mekanism integration in AE2, which worked around it. Thanks though :)
I have not been able to reproduce this in my dev or testing environments. You may want to try with the bugfix build I post later today.