Help Locating Crash

[salem]

How can I locate what's causing a crash? I've been getting 2 messages, it's always one or the other and they have the same "numbers". I've fixed all the leaks in my map, or at least most of them. There is no specific time at which the crash happens.

The memory could not be 'read'.

Exception: 0xC0000005 (ACESS_VIOLATION) at 001B:6F088E10
The instruction at '0x6F088E10' referenced memory at '0x00000074'
The memory could not be 'read'.

The memory could not be 'written'.

Exception: 0xC0000005 (ACESS_VIOLATION) at 001B:6F4D7CC9
The instruction at '0x6F4DCC9' referenced memory at '0x000000A8'
The memory could not be 'written'.

 

[Tom Jones]

Do you really think that the information you posted will help us narrowing down the problem? It's properly a trigger that causes the crash, so you'll have to test all of your triggers ingame to see which one is causing the crash. When you have found it, you can fix the problem or post the trigger so we can help you.

 

[Duwenbasden]

You do realize the memory location is different everytime you run the program?

 

[toast]

All I can tell you is that a memory read error essentially means you referenced a null pointer somewhere. Some things like this the compiler doesn't catch, I remember once I was banging my head against the wall trying to find the source of the crash, turns out I had asked for the player with index 0. Long story short: make sure your variables and things are set before you use them.

 

[salem]

You do realize the memory location is different everytime you run the program?

Well every time i get the crash it tells me exactly the same thing. I've taken screenshots to see if the numbers change or not... and they're not changing.
These numbers are displayed for a reason, the reason why i posted them here is to see if someone knows what they mean.

I'll recheck all my variables. The crash is somewhat random, sometimes it happens and sometime it doesn't, so i'm guessing it's a variable related to player activities in the game.

 

[WindexGlow]

I know I've crashed my game several times when I accidently put 'none' in pathing before, if you have alot of units/rarely used custom units, that might be the problem.

 

[call me Mike]

Did the map you were trying to play have any custom models or textures?

If so than the game is having trouble finding or locating them on your map. I had the same problem and your error message looked the same as mine. What i did to fix it was to DL the latest patch and it worked fine. If you already have the lates patch than unpatch the game and redownload it and patch again.

I'm not 100% positive that that is what it is but you could give it a shot.

 

[Mr Zero]

Alright if the numbers is the same when we can conclude it is the same trigger do it. Now do you have any triggered spells? If so try click them (If possible) and see it crashes.

You need to post your triggers. I can only be guessing.

 

[salem]

post my triggers? lol there's 2 many. But thanks for the offer.
I'll try everything that can be tried on the map and see if i can find what's causing the crash.

What I'm afraid of is for the crash to be involved in some simultaneous action requiring 2 or more players. That is something that I cannot test for since it involves 2+ players. I was hoping that someone would be able to make sense out of these numbers and hence helping locate the source of the crash, be it a variable or a model or whatever.

The crash is really random... sometimes the game goes on for over 40 minutes and nothing happens, and sometimes it crashes at around 13min... I can't seem to find a pattern.

I do have a custom model, it's a "hero glow" model. I use it for custom heroes. it seems to be working fine; the heroes with the custom glow work fine and the model is there as well.

 

[Tom Jones]

I'm allmost certain that nobody in the entire map community can make any sense out of those numbers. It's a memory reference, and since the memory references changes from game to game it's impossible to locate the problem from those numbers.