Memory Leak
A memory leak is a defect in which a program fails to release memory that is no longer needed, gradually reducing available memory over time.
“A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Memory Leak?
Memory leaks may cause applications to slow down, become unstable, or crash after extended execution due to exhausted memory resources.
Resource management: Unused memory remains allocated unnecessarily.
Performance degradation: Available memory decreases during execution.
Detection: Dynamic analysis and endurance testing commonly reveal memory leaks.
Real World Example
A regulated product team is preparing a release where Memory leak appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Memory leak as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Memory leak and similar ideas.
The page becomes useful in practice because Memory leak is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Memory leak in the context of ISTQB terminology?
Question 2
A tester needs to explain Memory leak to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Memory Leak. Test your understanding with topic-specific questions in our Mock Exams.