• Check out the results of the Techtree Contest #19!
  • Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!

[Crash] How to Read and Fix Fatal Errors?

Status
Not open for further replies.
Level 11
Joined
Aug 6, 2009
Messages
697
I'm getting a fatal error with an ability that doesn't happen everytime I cast it. In fact, I can use it plenty of times before it crashes. Sometimes I only have to use it a couple times before it crashes. Even when I use it without any enemies in the AoE of the ability, it crashes.

Edit: I believe the issue may have been 3 unit group leaks I just found (I thought I cleaned up after myself). Regardless, I'd still like to know how to read a fatal crash log if anyone could inform me.
 

Attachments

Last edited:
Without access to the build symbols and source code, which only Blizzard has, such files are of very limited use. For example I cannot get any useful information from them.

It might be a good idea to debug the spell. Set up an automated cast test case. For example have dummies cast the spell multiple times per second against various targets. If this reliably recreates the crash after some period of time then one can start looking into diagnosing the cause by manipulating the triggers until the crash stops or happens more/less frequently.
 
Without access to the build symbols and source code, which only Blizzard has, such files are of very limited use. For example I cannot get any useful information from them.

It might be a good idea to debug the spell. Set up an automated cast test case. For example have dummies cast the spell multiple times per second against various targets. If this reliably recreates the crash after some period of time then one can start looking into diagnosing the cause by manipulating the triggers until the crash stops or happens more/less frequently.
I managed to figure out the source of the crash here. Also, that sucks that there isn't any useful information from these logs.
 
At some point after blizzard came back, they ruined the crash logs to the point where they are basically useless now. There is no stack dump anymore, which often contained the name of the jass function that caused the crash, and because of their new anti-cheat-system you can't put a breakpoint at the crash location anymore either.

If you have a chance to downgrade to an earlier version of warcraft before they screwed that up, you might get some useful information out of them, but right now you're out of luck.
 
Status
Not open for further replies.
Back
Top