Leaks blame who?

[Striker21]

Hi,
Today is a nice day to talk about a ugly problem on Triggering:
Since i want to know what you all think about the question, so i'll call for a vote
Our votes today will be:
Who should you blame for why "leak exist" ?
And our contestants are:
Blizzard
Myself - for not destroying the leak
The one who let us know about leaks

Thank you

 

[Adiktuz]

Blizzard... because the question was Who should blame for why leak exist... Even without you or the other's leak will still exist because of Blizzard

 

[Dr. Boom]

I would blame you or myself.
1) I know about leaks!
2) Against the knowledge I still use them!
3) Against the knowledge I still use and don't clear them!

Reaction: Burn GUI
Solution: Use Jass

 

[ap0calypse]

Blizzard... because the question was Who should blame for why leak exist... Even without you or the other's leak will still exist because of Blizzard

A leak only exists if you do not remove it.
If you do remove it, there are no leaks and there wouldn't be anyone to blame.
For this reason, I blame "You".

A better garbage system could have helped clean the leaks, but the user is still the last link in the puzzle.
The only reason why Blizzard is also to blame is because they don't mention leaks anywhere, so the map maker can always use ignorance as an (in this case rightful) excuse.

 

[defskull]

You cannot read what human mind can think (actually you can - that is why AI exist), but at times, human will think beyond than that, like you do not want to remove the leak at that time (cause' you want to use it for other event and destroy it later), that is why leaks cannot be determined by a simple system.

Because you simply can't order the trigger maker to destroy his/her own variables, it is up to them to think when to destroy it.

 

[PurgeandFire]

Yeah Blizz could've implemented a garbage collector, but I doubt they anticipated WE to be as popular as it was.

Leaks are really easy to fix though. I don't think it is too much of a problem once you understand how it works.

 

[Dr Super Good]

A combination of Blizzard for having leaks that cannot be fixed (strings, units) and you for leaking stuff that can be fixed (locations, groups).

 

[WaterKnight]

You cannot read what human mind can think (actually you can - that is why AI exist), but at times, human will think beyond than that, like you do not want to remove the leak at that time (cause' you want to use it for other event and destroy it later), that is why leaks cannot be determined by a simple system.

Leaks are labelled to as leaks when you do not have the possibility to free the occupied memory anymore. If that is because of reference-loss, you cannot clean it manually or call them for other actions. Garbage collectors detect objects/memory the coder loses access to within his language interface. So no, it is not about AI or reading the coder's intention.

 

[mckill2009]

Blizzard didnt do their job well when cleaning those unneeded allocations...maybe they know that people like vexorian and
other good coders will ultimately discover the leaks in time, but found a way of cleaning it...