Server Status Thread

[Scaramouche]

Can we PLEASE know what the bug was, when you solve it, just for the sake of curiosity and love for your work?

you could be 99% sure that it was NullPointerException

[ChildhoodObesity]

Could we get a slightly longer (like 15 seconds) warning before shutting down the server so we have a chance to put down lifted stuff?

yea for real heheh im stuck outside walls outlawed nad have to wait till its back up to go to bed or w/e!

[loftar]

Sorry, that last restart was apparently unnecessary. I had just failed to entirely recompile my dev server when testing the bugfix. :P

Could we get a slightly longer (like 15 seconds) warning before shutting down the server so we have a chance to put down lifted stuff?

Sorry, I just want to shut down as soon as possible when I discover potential memory-corrupting issues.

[DaniAngione]

Sorry, that last restart was apparently unnecessary. I had just failed to entirely recompile my dev server when testing the bugfix.

Can you please go and sleep some after it's fixed?

[loftar]

Can we PLEASE know what the bug was, when you solve it, just for the sake of curiosity and love for your work? :D

Basically, I had named the wrong callback function on wound timers after sleeping, which caused the timer recorded in the wound not to get nulled out when expiring, in turn causing that timer to be doubly freed later on when the wound was freed. In the case of the original crash, this took the shape of freeing a completely unrelated data structure (an indexing structure for claims) that had simply happened to get allocated at the same memory address that the timer had previously resided at, causing its memory to be reused for other things (judging by the patterns of the data having overwritten it, an obstacle cache) while still being referenced.

Can you please go and sleep some after it's fixed?

Will consider. ^^

[boreial]

joyous rhapsody server crash

[joojoo1975]

well damn, seems it wasn't all squared away, or something new has popped up, either way, time for sleep(I guess)

wish you good luck in finding the probs

[Oniwaski]

Aww dern. Them's some rough bugs today.

[Scaramouche]

Can we PLEASE know what the bug was, when you solve it, just for the sake of curiosity and love for your work?

Basically, I had named the wrong callback function on wound timers after sleeping, which caused the timer recorded in the wound not to get nulled out when expiring, in turn causing that timer to be doubly freed later on when the wound was freed. In the case of the original crash, this took the shape of freeing a completely unrelated data structure (an indexing structure for claims) that had simply happened to get allocated at the same memory address that the timer had previously resided at, causing its memory to be reused for other things (judging by the patterns of the data having overwritten it, an obstacle cache) while still being referenced.

Can you please go and sleep some after it's fixed?

Will consider. ^^

See what I've been talking about, lol?

[Myrgard]

jorb

Please restart the loftar bot, it seems to have crashed again