[!]Handle Pointers get reset

I bet somebody would like to store values of a handle (unit, trig, etc) by gamecache with return bug. But I found that it's unsafe.

For example, if unit A's pointer is 12345678. When it dies, it will be removed when its corpse faded. Then 12345678 refers to nothing. But when a new object is created, it will use the empty pointer number again. So maybe a new-created unit(or trig, timer, location, or whatever) will have the pointer 12345678.

And as a result, if you store some value, and uses the unit's pointer as the key. When you use the same way to load the value of unit B, you'll load unit A's, not empty value. :<

It's unsafe isn't it? Does someone have an idea to solve this problem?

remove the refference when the unit dies

I don't think it always work, for example, what if the unit can be revived??

It is possible to set the amount of time corpses stay, so you could do something like:

Set corpse stay to 75 seconds

On Unit Death:
Wait 70 Seconds
If Unit Still Dead - then - remove corpse, reset cache data

That way you get 70 seconds of corpse stay with the corpse removed and the data removed at the same time. If the unit comes back, no big deal because it handles that. The only thing it DOESNT handle would be if the unit comes alive again and then dies again after 69 seconds, it would be removed instantly. This can be fixed, but it is more complicated than I care to explain

Are you sure that it reuses pointers. I think it just keeps going upwards untill it comes up to a limit, where the emergency garbage collection thingy kicks off, and then it starts reusing old pointers.

But if this is really a concern, you can use this quick fix that should work:


If you call this function with a handle, it "should" never be re-used, if our theories are correct. But please note that this is only a concern if you're a vivid leak-fighter and allways null your local handles.

~Cubasis

The likely hood of it happening is low. If you worry then put controlls in the situation to make it more managable.

For units, you can just wait till their maximum life is 0

Yes I am sure. You can test for yourself.

Why?

Because since locals that aren't set to null leak, that will also make sure the handle never derrefferences in theory