Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am new to memory leaks and memory profiling. Kindly can anyone help me out in finding the answers of the below mentioned questions

When to check a memory leak, during coding phase or testing phase? Who is responsible for identification of memory leaks, Developer or Tester? What is the best time to identify a memory leak?
Who is responsible to run a memory profiler like ANTS (Developer or tester) ?

share|improve this question

migrated from May 28 '13 at 14:01

This question came from our site for professional and enthusiast programmers.

up vote 4 down vote accepted

It's best to look for and identify all issues as early as possible. The QAs can pick this stuff up, but by then in a sense it's too late.

You should (as a developer) look to identify and mitigate such issues as early as possible and design for them, rather than patch post-development.

It's an oft-stated maxim that to fix each bug/issue in a successive stage of development costs 10x what it does in the earlier stage (different figures are quoted sometimes but the magnitude remains the same), and as such resolving or avoiding issues as early as possible is the most desirable (cost-effective) outcome.

share|improve this answer
We have a web application(already developed) and we are facing memory leaks issues at client side. we are discussing on how to best implement memory profiler to identify memory leaks at this stage. so at this stage should the QA take it up and identify the issues, and for the long term(later releases) developer will have to look into this during development and QA should only cross verify via Memroy profiler? – JHaider May 28 '13 at 9:43
Off topic but the oft-stated maxim might not actually be true - read The Leprechauns of S/w engineering... – Phil Kirkham May 28 '13 at 14:21
I agree, this is typically the job of the developer, however it sometimes is directed by me due to some performance/stress testing that I have been doing and noticed memory spikes or memory leaks. – Sam Woods May 28 '13 at 18:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.