flatbield

In project management lore there is the tripple constraint: time, money, freatures. But there is another insidious dimension not talked about. That is risk.

The natural progession in a business if there is no push back is that management wants every feature under the sun, now, and for no money. So the project team does the only thing it can do, increase risk.

The memory leak thing is an example of risk. It is also an example of some combination of poor project management including insufficient push back against management insanity and bad business mangement in general which might be an even bigger problem.

My point, this is a common natural path of things but it does not have to always be tolerated.

I get your point but I do not think you should justify releasing crap code because you think it has minimal impack on the customer. A memory leak is a bug and just should not be there.