Tinkers Construct Crash

Question

Tinkers Construct Crash

yepidoodles opened this issue 8 years ago · 12 comments

yepidoodles commented 8 years ago

SlimeKnights/TinkersConstruct#2776

thiakil commented 7 years ago

🤔

Utildayael · Answer 1 · 2017-02-19T19:36:51.000Z

Ya this has been a bug for a long time. The workaround is to turn off the item rendering in Tinkers but that sucks. Something Mek is doing really pisses it off and makes you crash to desktop repeatedly while crafting some stuff in there. Haven't found a trend as it seems to be random but I know I was making a jetpack once on a crafting table and it did that.

yepidoodles · Answer 2 · 2017-02-19T19:52:41.000Z

As far as I can tell it's due to the excessive amount Mekanism uses NBT data.

Utildayael · Answer 3 · 2017-02-20T00:38:57.000Z

Gotta be honest, this bug has been around for at least 6+ months, possibly entire life of 1.10.x Mek. I think I have an open bug on it too...

…

On Feb 19, 2017, at 1:52 PM, yepidoodles ***@***.***> wrote: As far as I can tell it's due to the excessive amount Mekanism uses NBT data. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

aidancbrady · Answer 4 · 2017-03-08T23:45:29.000Z

I've tried every logical and hacky fix to get the TC rendering working but I just can't seem to figure it out. Closing, but I'll still try and find a fix when I have a chance.

Utildayael · Answer 5 · 2017-03-09T00:54:07.000Z

Thanks Aidan. This thing has been hell since it's a full client crash.

…

On Mar 8, 2017, at 5:45 PM, Aidan ***@***.***> wrote: I've tried every logical and hacky fix to get the TC rendering working but I just can't seem to figure it out. Closing, but I'll still try and find a fix when I have a chance. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Bluexin · Answer 6 · 2017-03-11T02:02:33.000Z

What I've done on my end (band-aid solution) was just a try-catch to ignore the error. Renders still fine in the world etc and just doesn't render as a model on top of the Tinker's Crafting Station.
@aidancbrady

OrdinatorStouff · Answer 7 · 2017-11-06T18:44:23.000Z

Per #4798 @Alphanos discovered a link to alwaysSetupTerrainOffThread Forge config as having an impact on whether this crash happens or not. Perhaps this is new clues to tracking down what could be causing these Tinker's render issues?

thiakil · Answer 8 · 2017-11-07T01:14:28.000Z

@OrdinatorStouff we fixed this in Mekanism a while ago by checking for an OpenGL context before doing the hacky stuff. Any relation to it happening in the recent issue with Mekanism items is likely coincidence.

We check for device capabilities which will throw the no context exception (which we catch). I'm not sure how that would cause issues with the thread that actually has the context.

Alphanos · Answer 9 · 2017-11-07T02:03:34.000Z

If the current crash involves Mekanism items only by coincidence, does that mean that I should be reporting the current issue to Forge? I don't have much experience knowing whether Forge issues are typically reported by end users or by mod developers. Thanks!

thiakil · Answer 10 · 2017-11-07T02:07:24.000Z

If it's crashing in a Tinkers table, likely no.

Can it be reproduced with just Mek & Tinkers & alwaysSetupTerrainOffThread?

Alphanos · Answer 11 · 2017-11-07T03:30:14.000Z

Can it be reproduced with just Mek & Tinkers & alwaysSetupTerrainOffThread?

Yes. When alwaysSetupTerrainOffThread is enabled, the crash can be reproduced with only Mekanism and Tinker's Construct.

Share to