Error: object .?AVC3Vector@NTempest@@

[XanderD]

Hi everyone!

I have been working from time to time on a map project I started about two years ago. Now I'm getting close to finishing it, but I got a problem. In every test run the game crashes at around 2h and 46 or 47 minutes (which is at or around 10 000 seconds). The error message is always according object .?AVC3Vector@NTempest@@ . Since this error is so consistent about the timing I first thought it was an error with some trigger. There are a few triggers of the kind "every x seconds" and also some of the "time elapsed" time. Of the latter there is not a single one that triggers anywhere near that time mark. The "every x seconds" trigger get triggered hundreds or thousands of times before the error occurs. Nevertheless I tried if it was one of them by changing the trigger-intervals but the time the error happened kept the same. Can anyone tell me what kind of error this could be or what this object .?AVC3Vector@NTempest@@ is so I could check in that direction?

thanks in advance!

 

[Deleted member 219079]

Could be a memory leak:

"Memory Leaks" - How do I find em?
Complete list of things that leak
Things That Leak
Memory Leaks

 

[Bitchmoon]

is NTempest one of your regions/any other variable/instance names?

 

[DracoL1ch]

[Tool/Hack] Unreal Jass Spy v4.0

 

[XanderD]

Thanks for your help!


jondrean:
If it is a memory leak by one of these triggers I'm still confused why it is so consistent about the time it happens. I have a lot of triggers of several kinds described in the threads you linked. But I guess I have to start reworking my hundreds of triggers.


Bitchmoon:
No, it's not and frankly I don't know what exactly it is.


DracoL1ch:
I didn't use JASS - can that tool still help me?

 

[Deleted member 219079]

I have a lot of triggers of several kinds described in the threads you linked.

Then leaks are the probable cause.

 

[DracoL1ch]

There are a few triggers

I didn't use JASS

pick one. but if you're missing any knowledge about it, its useless for you

 

[XanderD]

It probably was a memory leak. I overworked my triggers and had the game run over the last two nights and it stood stable for seven and nine hours respectively.

Thanks again!