Memory Leak Trigger

[Dreknethema]

I need help cleaning up the memory leaks in one of my triggers.



Any ideas?

 

[Razer!X]

Don't every 0.01 second. Change it to 0.03 or 0.04 it works faster. And also don't use Integer A but use your own integer variable.

 

[Solu9]

Remove the "Do Nothing"'s because they do nothing. Just leave those actions blank.
I'm not sure, but I think you leak a player group 2 times for every loop.

Also, there is no need to run this trigger every 0.01, you can go as high as 0.1 imo. But at least raise it to 0.03.

 

[Dreknethema]

Trying it now.

 

[PurgeandFire]

It is better to right click the trigger, copy as text, and place them between [TRIGGER][/TRIGGER] tags. It'll be easier for us to read and respond.

Anyway, the leaks come from the "Position of..." functions. Those are leaking points. To fix it, create two variables:

• Set SurvivorPoint = (Position of Survivor[(Integer A)])
• Set SeekerPoint = (Position of The Seeker 0012 <gen>)
• Hero - Modify strength of Survivor[(Integer A)]: Set to (Distance between SurvivorPoint and SeekerPoint)
• Custom script: call RemoveLocation(udg_SurvivorPoint)
• Custom script: call RemoveLocation(udg_SeekerPoint)

Check out some of the tutorials on leaks on this site and world-editor-tutorials.thehelper.net. If you familiarize yourself with leaks, you'll have a much nicer time coding without worrying about chewing up memory.

 

[Dreknethema]

I tried choo's variable idea, it failed miserably. But the mutual idea of raising the 0.01 to 0.03 seemed to slow down the leak noticeably.

I'll work on the other stuff when I have time to do more. Thanks everyone!

 

[Vinz]

If you replace Integer A with an Integer variable you have to replace everything referencing to Integer A as well.

 

[IcemanBo]

You don't need "And - All Conditions" block. Just add conidtions without the block.
Player[loopIndex] should be stored into a tmpPlayer variable.

Don't every 0.01 second. Change it to 0.03 or 0.04 it works faster.

0.01 is not needed here, but how 0.03 works faster?

 

[Dreknethema]

If you replace Integer A with an Integer variable you have to replace everything referencing to Integer A as well.

Thanks but that's kind of common sense..? It didn't work for some reason in either case.

 

[Nichilus]

Changing IntegerA for your own variable does not prevent leaks, but it's more efficient and generally better for various reasons.

Leaks are where you modify hero's strength. The (position of *something*) leaks. Look at post #5 - purge already wrote how to solve the problem.

 

[Dreknethema]

Changing IntegerA for your own variable does not prevent leaks, but it's more efficient and generally better for various reasons.

Leaks are where you modify hero's strength. The (position of *something*) leaks. Look at post #5 - purge already wrote how to solve the problem.

I incorporated #5 into the trigger, works fine. Its the Integer A variable that I tried making that didn't work.