I got wierd problem in my map.

In my halo map, the game start correctly, all triggers are working. only problem, some people are lagging..

but, afther like 10-15 mins, problems start to occur: some triggers stop functionning, or funcion half of the time, and the longer the game last,more triggers are being screwed up. plus, this seems to cause alot of lag to some players.

afther like 30 mins: shield regenerates only 1/4 of the time, sometime players dont respawn when killed, sometime reloading dont give you any ammos, sometime you can equip 2 weapons at the same time(in the same hand, giving you abilities of both), then, overheat totaly stop functionning,and, like if it wasn;t enough, lag make the game unplayable (not for me but for alot of players)

the first 10 mins is perfect,all triggers are working, all functions are 100 % operative(but lag).

ive heard leak cannot disable triggers.
if its not leak, then what is it?


id be glad if anyone could help me

Leak shouldn't stop triggers from occuring, but if they are clogging your computer's resources so badly that its choking and sputtering, I would think it's possible for periodic events/checks/etc. to start getting missed...
This is just speculation though :|

exactly, triggers in wich i have the MOST problems are the triggers with Event: Every 0.0X Seconds of game time

Periodic event triggers do not leak by themselves. The reason for this is not the trigger itself that is leaking, but the code that it runs leaks memory. So in periodic events, your code leaks again and again every 0.0X seconds, which adds up pretty quickly.

Post your code, and people will be able to help you figure out where your memory leaks are occuring.

[quote=Vuen]Periodic event triggers do not leak by themselves. The reason for this is not the trigger itself that is leaking, but the code that it runs leaks memory. So in periodic events, your code leaks again and again every 0.0X seconds, which adds up pretty quickly.QUOTE]

main problem is not the LEAK, its the fact of having my triggers disable or only half-functionning.



as for my code, i have absolutly no clue what's causing leak, and i have many 0.0x triggers. all of them use variables, and "call DestroyXXXX (udg_variable)" to avoid leak.

That is...bad...very bad. I have none, in any of my maps (ok, in some cinematic maps). Sometimes I use 0.0x temp triggers for pushback type effects, but they use timers which are paused when not needed.

Yes, and I'm telling you they become half-functional or disabled because they leak.

When you leak too much memory, your computer starts churning away trying to sort it all, which takes a lot of CPU power. So it can't run your triggers every 0.0X seconds anymore because it just doesn't have enough power; they get ran when Warcraft gets the chance, which could take many seconds since you're leaking so much memory. It quite simply can't keep up, because it's too busy pageing leaked memory.

Fix the leaks, and your triggers will keep working.

Mine ARE needed. for all AMMO-MOVING triggers,flag detection and all shield-detection triggers.

Yes...but you need to make sure all your leaks are cleaned up. That's what's causing your problems, as Vuen just explained..

it's not always leaks, I suggest if you find all leaks are cleared and this is driving you nuts, just try and find another way to do it, more than likely the second way will fix the problem, just dont make it similar. You don't always have to know what a problem is to fix it.

The method is a bit crude but much better than waiting for one us to help you :P

ive fixed all leaks. this is an example of one of my triggers


This is another example.




theyre all like that. all used variables, and then custom scripts to destroy them.Also using second triggers to ONLY turn on the 0.0X Triggers when required, then turning them off instantly afther. it should NOT leak...

Actually, you still have several bad leaks in there:


You're leaking a unit group there, with the "Units within ..." command. Unit groups are the worst kind of leaks; this is the kind that will make Warcraft crawl. You handled the other groups perfectly. Don't forget this one.

Here's another leak:


Another bad unit group leak (Units within 80.00...), with a location leak (Position of...) to boot.


The second trigger leaks a special effect. Special effects attached to units leak very little actual memory, but the meshes hang around, so as they add up they make your graphics card crawl. A good way to do this would be to attach the handle of the special effect to the unit with a gamecache, that way when you create a second special effect on the same unit you can destroy the first one.


Fix those up, and check your other triggers for leaks again (mainly the "Units within range" function) and try it out again to see if your triggers still stop working after a while.

Also, in the first trigger you set TempPoint3 inside the second loop, but don't destroy it within the loop. Also, it might be very useful to try and convince someone to convert those into JASS and make them more efficient, because you are doing a hell of a lot every 0.05 seconds in that one trigger alone.

i have 7 triggers like that, some have a 0.02 delay too..(sniper)

BUT! the trigger is turned ON everytimes a unit shoot, and OFF when the last unit of type "Missile - Flames" Die. so its ONLY used when required.

what about now?