Page 1 of 1
[0.15.31] Stopping the server due to an unexpected error
Posted: Mon Jul 31, 2017 9:10 am
by die_8_
Attach saved data and logs.
Re: [0.15.31] Stopping the server due to an unexpected error
Posted: Mon Jul 31, 2017 12:45 pm
by 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.
Re: [0.15.31] Stopping the server due to an unexpected error
Posted: Wed Aug 02, 2017 9:46 am
by Dev-iL
kovarex wrote: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....
Re: [0.15.31] Stopping the server due to an unexpected error
Posted: Wed Aug 02, 2017 11:13 am
by kovarex
Dev-iL wrote:kovarex wrote: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 ..