Leak Check

[BloodDrunk]

Can someone point me to the program called ''Leak Check''?
I heard about it, but cant find a Link...

 

[Squiggy]

http://www.hiveworkshop.com/forums/tools-560/leak-check-3-1-a-62951/

It stinks, tho.

 

[TwoVenomous]

the tool didn't work properly, the creator didn't update the tool anymore.
it's not recommended at all and buggy.

but if you only want to know the link, here it is Leak Check 3.1

 

[defskull]

The best Leak Checker tool is a tool that we all have - Brain, use it wisely.
It's not that hard to learn about leaks and how to clean them, really.
It's about logic.

 

[BloodDrunk]

how dangerous for my map it is? Can it check something correct nd check it as wrong or?

 

[BloodDrunk]

The best Leak Checker tool is a tool that we all have - Brain, use it wisely.
It's not that hard to learn about leaks and how to clean them, really.
It's about logic.

I know how to remove leaks... But I have lot of triggs and it's boring checking every trigger to see if it leaks

 

[TwoVenomous]

how dangerous for my map it is? Can it check something correct nd check it as wrong or?

it's not dangerous for your map, but the checker is not accurate.

 

[BloodDrunk]

ok then

 

[millzy]

leaks will cause the map to lag

 

[defskull]

But I have lot of triggs and it's boring checking every trigger to see if it leaks

If you're boring to check the triggers, why won't you be boring in developing your map ?
This is not a flame, but more of a words for you to think deeply on your actions.

 

[Dr Super Good]

Excessive leaks can result in degraded map performance and potentially even out of memory errors (with a crash) when the user's page file is exhaused or the virtual memory address space for the process is exhausted.

However generally leaking too much will cause frames to be dropped and crash WarCraft III due to internal resource exhaustion long before memory becomes a problem on a modern system.

Be aware that not all leaks can be fixed. WarCraft III is a very buggy game and has its own memory leaks.

Leaks that cannot be prevented.
String: Every unique string you generate in JASS (which GUI compiles to) will stay in memory until the map session ends. After enough unqiue strings are leaked it will become performance intensive to perform any string operation.
Unit: Every time a unit is created a bit of memory is leaked. No mater how the unit meets its end it will still result in a permanent memory leak. Whether it dies of natural causes, killed by triggers or even removed by triggers the same leak exists.

Leaks that can be prevented.
location: After creating a location you can call the appropiate destructor on it (RemoveLocation).
group: After creating a group you can call the appropiate destructor on it (DestroyGroup).
effect: After creating an effect you can call the appropiate destructor on it (DestroyEffect).
force: After creating a force you can call the appropiate destructor on it (DestroyForce).

There are other destructors as well but those are the most common.