NoQ uploaded file warzone2100.gdmp-AjCu6b (24.9 KiB)

NoQ commented

Ah, found the old crash. By the way, had a closer look at the new crash, and it's not really related to the burn damage, yet still looks very similar.

NoQ uploaded file warzone2100.gdmp-23aeac (27.5 KiB)

NoQ uploaded file warzone2100.gdmp-VMb6yA (25.8 KiB)

Yet another similar dump.

Per changed title from A certain crash in incendiary damage code. to Crash in map grid iterator

Per commented

Several crash dumps in this ticket, all pointing to gridIterate () at mapgrid.h:57.

Reg312 commented

Tried to reproduce this crash on my windows build, but unsuccessful

NoQ commented

Since nobody can reproduce that, i wonder if it's related to the fact that i now use js_enumRange() in my scripts, which also uses gridIterate().

Cyp changed _comment0 which not transferred by tractive

Cyp commented

Note the nearby comment »// Detect (by crashing in a reproducible way) if calling gridIterate() again before gridStartIterate().«, which may be relevant.

Doing something like

gridStartIterate(something)
while(gridIterate())
{
    gridStartIterate(somethingElse)
    while(gridIterate())
    {
        doSomething();
    }
}

will crash there, since the inner loop clobbers the outer loop.

NoQ commented

Is there any way for me to gather more information? Probably somebody could provide a patch that would expose more relevant debug data?

Cause i'm able to reproduce it very often, but absolutely unreliably.

Cyp changed status from new to closed

Cyp changed resolution from `` to fixed

Cyp commented

"Auto"closing ticket. Don't know where the issue was, but should probably be fixed now, since there's nowhere for it to hide, now.

commit 5c7788784b653cae0fdf80ad687c4aec2c58a3f5
Author: Cyp
Date: Sat Feb 9 12:33:00 2013 +0100

Change gridStartIterate interface to safely allow recursive calls.

Probably fixes #3894.

NoQ commented

Just wanted to mention that crashes seem to have actually gone, thanks all again (: