[General] Seek for: List of known reasons for Fatal Errors

[Eikonium]

Hey!
Does a list of possible coding reasons for Fatal Errors exist out there?
I only know one reason so far, and that is referencing to player(x), where x is below 0 or above 15.

Greetings,
Eikonium

 

[PurgeandFire]

Multiboards and leaderboards cannot be made on map initialization.

If you try to use any triggers/functions on a lightning that was destroyed, it'll crash.

This list has a decent amount as well. It is worth the read:
http://www.hiveworkshop.com/forums/world-editor-help-zone-98/list-warcraft-iii-crashes-194706/

But usually fatal errors should be handled case by case, apart from the really popular ones (which is usually because of (1) an object/faulty import (2) Player(x) index (3) lightning).

 

[Dr Super Good]

3.Pagefaults caused by too many memory leaks crash the game.

I would not trust that list. Seeing how pagefaults are invisible to processes...

 

[Eikonium]

Hmm, I can exclude nearly all listed reasons. Referencing to player(x) is the one I can't yet exclude.
Is there any possibility that removing a unit from the game can cause a Fatal Error? Maybe because any other triggers that use waits are still refering to the already removed unit, taking its playernumber (x) and then doing something with player(x)?

I just tried to reproduce such a problem, but I wasn't successfull. The game seems to always threat player 1 as the owner of removed units. So I am probably wrong with guessing that reason.

 

[Dr Super Good]

Is there any possibility that removing a unit from the game can cause a Fatal Error? Maybe because any other triggers that use waits are still refering to the already removed unit, taking its playernumber (x) and then doing something with player(x)?

Yes it is possible. I also think it is possible that removing units under certain event states can cause a crash (eg event queued on unit after another event but unit is removed before event executes).

The game seems to always threat player 1 as the owner of removed units.

It returns Player(0) as a safe default value as opposed to null since that would almost always cause a segmentation fault type error if used. Equally well things like Player(16) will cause a fatal error.

 

[Eikonium]

Yes it is possible. I also think it is possible that removing units under certain event states can cause a crash (eg event queued on unit after another event but unit is removed before event executes).

In my case, the Fatal Error happened, when a player left the game while still being alive. His remaining units got removed, and any trigger messed up, probably.
I will change that to killing all of his units instead and hope for the best