[1.12.2-0.9.1h] ticking branch crashing dedicated server

Question

[1.12.2-0.9.1h] ticking branch crashing dedicated server

kreezxil opened this issue 6 years ago · 5 comments

kreezxil commented 6 years ago

server crash report: http://paste.ubuntu.com/p/9CzDqCqKwH/

ferreusveritas · Answer 1 · 2019-01-01T17:44:59.000Z

Do you have any steps to reproduce this?

kreezxil · Answer 2 · 2019-01-02T12:38:46.000Z

No, but it crashed my server a few times. If you don't see anything in the report that can help you pinpoint where you might be able to make a fix then close this for now. At least it's been recorded.

ferreusveritas · Answer 3 · 2019-01-02T13:21:58.000Z

The log is so long that I couldn't see where the error originated. It's cut off. I'll keep it open for now.

kreezxil · Answer 4 · 2019-01-02T19:04:49.000Z

I can see all 2305 lines of that log just fine. Couldn't you just intercept a stack overflow error and write out to the debug.log that you intercepted it and then killed the thread associated with it?

…

On Wed, Jan 2, 2019 at 7:21 AM Ferreus Veritas ***@***.***> wrote: The log is so long that I couldn't see where the error originated. It's cut off. I'll keep it open for now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#193 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADs0iPNRd4AKBbgQRzQ6SWjgp_Ofq2SVks5u_LJ3gaJpZM4Zl3N1> .

ferreusveritas · Answer 5 · 2019-01-02T19:11:37.000Z

The backtrace portion of the log doesn't have a starting point. It's cut off. If I could reproduce the problem then I'd have more debugging options. I can see that it's related to the fire block from the log though.

Share to