[0.15.31] Stopping the server due to an unexpected error

[die_8_]

Attach saved data and logs.

[kovarex]

Unluckily for us, we catch the bad_aloc instead of crashing, so we have no idea what happened there. I guess that you can't reproduce it.
The only thing that came to my mind is bad allocation related to malformed packet that has proper crc value by a chance. We check on most of the places, but I found 3 other places where it could create such an error. It is shot in the dark, but it might help.

We should find a way to throw on std::bad_alloc right away, to see the stacktrace ...

Edit: I changed the code for 0.15.32 in a way, that bad_alloc will not be caught as an exception, so it will probably show stack trace of the error next time.

[Dev-iL]

Unluckily for us, we catch the bad_aloc instead of crashing, so we have no idea what happened there. I guess that you can't reproduce it.

So basically it was:

I kid, I kid....

[kovarex]

Unluckily for us, we catch the bad_aloc instead of crashing, so we have no idea what happened there. I guess that you can't reproduce it.

So basically it was:

I kid, I kid....

Nice pic Well, we logged the exception (it is in the log), but without stacktrace, it was almost useless ..