User Mohammed Sherif (firstname.lastname@example.org) posted:
Does any body has standard Memory Leak test document. If you have could you
please pass it to me.
Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com
Re: Memory Leak:
User (email@example.com) posted:
Since nobody else has replied... What exactly are you looking for? Memory
leaks are not planned features. They are something that should not occur,
but does. If you're looking for a strategy for identifying and resolving
memory leaks, here are some I've seen used:
1) Proactive Approach: Using past experience/knowledge of which areas you
are most likely to find them, perform code reviews and/or use debuggers,
tools such as Purify (the best one I know of) to find leaks during
development. This is most often performed by an experienced developer or
build meister. By identifying/fixing leaks early, you save time and money
and decrease the risk of shipping with serious bugs.
2) Reactive Approach: Investigate any problems found occur in black box
functional testing and/or beta test that might be due to memory leaks).
Code reviews, debuggers and Purify useful here.
3) Deny everything. Blame it on the test tool. Say there's nothing you can
do about it because (take your pick).