Fatal Error...?

So, I'm getting a fatal error in my map. The strange thing is that it happens only when I quit the map (exit program, restart mission, etc.; anything that ends the map), but at no time inbetween does a fatal error occur.

Where's the best place to start looking for the error? I would think systems, since I just replaced Vex's 1.24 versions back to the 1.23b (testing purposes) and it started then.

I use the following systems:

• TimerUtils
• Intuitive Damage Detection System
• Table
• Dusk's Knockback System
• Terrain Pathability (Dusk)
• LastOrder
• GroupUtils
• UnitIndexing Utils

do you run wc3 with grimoire ?
idk i have sometimes also this issue but couldnt find the exact source...

and yes grimore is the most logical problem for. (at least in my case it's so)

I can't run Grimoire because of the old 1.22 break and I haven't gotten a dual-install to work as of yet, so I can't really use that as an option.

well you can try and experiment what can cause it (if map isn't large)
try to disable/enable components. and instantly after load restart the map. and so until you don't get fatals. it's really interesting...

The only problem is I'd have to disable almost every trigger at once since a lot of my spells depend on systems like TimerUtils, so to disable that and still have the code parse (so that the testing would actually be useful) I'd have to disable everything.

Oh well, I'll work on it in my spare time. It's not a major issue, since it doesn't occur until the end anyways :P

I also experience this problem. At first, crashes would only happen after 2 minutes into the game after I restart/exit the map. I tried locating the source(s) and when I found one possible source and disabled it, the crashes happen less frequent (doesn't crash after 2 minutes too), but randomly after the 2 minutes. The source (I know this is a REALLY strange source) is destroying timers. So I suggest trying to commenting out the "call DestroyTimer()" functions. I also tried my map with no triggers at all, and I do believe it involves triggers.

The only DestroyTimer() calls are used by TimerUtils, and I doubt those are what's causing it. And the crash is immediate; if you go to the score screen, clicking OK causes it.

i never use it... just btw.