| || |
- 1 Post By JakeBrake
When would you report a memory leak?
How much memory increase would you consider to report as memory leak?
eg, if you find a process increase its private bytes about 1M per day and keeps its pattern for a couple of days, would you report it as memory leak? And do you think dev will try to fix it?
Look at the definition of a leak, which would have an expected result of come number of bytes always being allocated but not decallocated so you have a constantly increasing number of bytes in your committed pool for a given application set. If the number of bytes is static, even if high, oer a period of time then I would be not so concerned. A good example of this last condition is a database server which grabs a byte pool and a disk pool when it starts for direct management. But if I see the pool size increasing on a constant basis, een if that increase is small, this points directly to a leak and I would report it immediately
It's not only increase in memory but also releasing memory after certain duration- which one needs to monitor.
If the consumed memory doesn't hit the roof and the consumed memory is released then no need to report it as memory leakage otherwise even for smallest gradual increase without releasing it should be reported.
Hope it helps.
I agree with Mr. Pulley. Any suspicions of memory leak with objective evidence should be reported and investigated. There are gobs of tools to help detect memory leaks. My own personal computer atop my shoulders suffers occasional memory leaks. People around me are not afraid to report that to me immediately and recommend more Omega 3 fatty acids.