Page 1 of 1

Laborer has no action at start of ...UpdadeState

PostPosted: 20 Jul 2013, 21:31
by Plebsiak
Hi.
Haven't found this one in Bugs (i haven't searched it thoroughly, though).
At first there were few 'stack overflows' but then this happened.
I tried to resume but the same Laborer ((143;190)) fires it up again.
For now only the image with call stack of the main thread.

Image


I can provide with the replay and other information if you wish it.

Let me take this opportunity to express my appreciation to you for the remake.

Re: Laborer has no action at start of ...UpdadeState

PostPosted: 21 Jul 2013, 06:41
by Krom
Usually when one error occurs the game becomes unstable and all sort of bugs and glitches can happen afterwards. Only the initial error matters. All subsequent errors are just consequences of that initial error.

Re: Laborer has no action at start of ...UpdadeState

PostPosted: 21 Jul 2013, 12:22
by Plebsiak
I can recreate the first error by playing the replay.
However, Windows is instantly proposing to close the app, so i can't use the madExcept.
Only 'valuable' text i can read is this line:
"Exception occured: EStackOverflow: Stack overflow"

If you could somehow prevent OS from intervening it would be possible to retrieve more information.

I wasn't prepared for debugging the remake because i've never had any errors.
I will be more careful next time and catch the first one.