WC3 crashes

Is there any list or something of things that crash warcraft?

Apart from stupid things like ExecuteFunc ("blablabla") or Player (16).
It would be really helpful to use as a checklist for debugging maps - because often you get something that looks very much like a random crash.
Can a crash possibly happen because of accumulated small bugs like not clearing something/releasing something incorrectly (e.g. it will not crash if you do it a few times but it would eventually crash if it happens every minute or so - making it extra hard to debug).

Infinite loops, divide by 0, and maybe even large amounts of accumulated leaks and bugs can cause issues. I dunno if they can crash wc3 (sounds like a FATAL ERROR), but I know they can cause some problems.

And a Wc3 crash-list would be pretty helpful, especially with War3err being unusable right now.

Having structures with no models can sometimes cause crashes as well.

Hmm I added a trace function call into every function in the map (in a debug block) - its not very useful because it prints a lot of text and you wont have time to see anything when it crashes.
But next I think I will save the information into gamecache (its singleplayer so gamecache would be persistent) and tada - we have stacktrace. That would detect problems other than accumulated bugs.

Ahhh I've encountered lots of crashes in my maps before. It's most likely an infinite loop, which sometimes can be very very hard to find. I usually throw in debug messages so I know what was the last thing that fired before it crashes. Try looking at any triggers that run other triggers, or if you have something that tries to decide something randomly.

Never allow null into natives.