Unexpected error in both editor and in-game

[Richardik]

Hello, last 2 weeks I am frequently experiencing the following error in one of my maps, it happens randomly either when map is opened in editor(which results in editor crashing) or in test map game(which results in game crashing, with editor staying intact).

Including the .txt files from error folder, War3Log.txt is not present in every error.

Any ideas what the culprit could be? Thanks.

 

[SpiritTauren]

I had the same error once, simply when I clicked with left mouse button on terrain of my map, without selecting anything from the tool palette.

 

[Swatosj]

I'm not sure the two files you provided will help but I'd suggest to read this if you didn't already: [Crash] - List of WarCraft III Crashes

Also is it an old map from a previous version of war3 that you did open in 1.31 editor ? Some maps are crashing since 1.30 and I've heard it could be linked to GUI comments that need to be removed before opening the map in a newer editor.

 

[Richardik]

I had the same error once, simply when I clicked with left mouse button on terrain of my map, without selecting anything from the tool palette.

Used to happen with my map as well, somehow it fixed itself though.

I'm not sure the two files you provided will help but I'd suggest to read this if you didn't already: [Crash] - List of WarCraft III Crashes

Also is it an old map from a previous version of war3 that you did open in 1.31 editor ? Some maps are crashing since 1.30 and I've heard it could be linked to GUI comments that need to be removed before opening the map in a newer editor.

The work on it started on 1.30.4, object and trigger data was copied over to the new base map created in 1.31.

 

[SpiritTauren]

Used to happen with my map as well, somehow it fixed itself though.

Fixed itself? Wow. Go figure...
Man, you know that feeling when you've just finished checking all bugs and are good to go, but no, something new happens. No matter what I do, there's always some new error popping up with new patch =( So demoralizing.

Spoiler

[Crash] - Different PC spec influence on trigger length/execution quality

Everything runs like a babe, but then you test your map on an older laptop that used to run Wc3 like a beast, and it turns out that the code isn't executed in a correct manner, depending on PC specs (if you tend to use large arrays, hashtables etc.).
So, to sum it up: someone here (sorry, can't recall who exactly) wrote once "another year of broken world editor" - I guess that is so, after all.