LeakSanitizer: detected memory leaks

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

# Build with symbols so the stack traces are readable
g++ -g -O1 -fno-omit-frame-pointer -fsanitize=address main.cpp -o app
./app

# Longer stacks for leaks allocated deep in a call chain
ASAN_OPTIONS=fast_unwind_on_malloc=0 LSAN_OPTIONS=malloc_context_size=30 ./app

# Suppress a known leak in a library you do not own
echo 'leak:libfontconfig.so' > lsan.supp
LSAN_OPTIONS=suppressions=lsan.supp ./app

# Leak checking without ASan overhead
g++ -g -fsanitize=leak main.cpp -o app && ./app

How to diagnose C++ errors

C++ errors fall into two very different worlds. Compile and link errors (undefined reference, multiple definition, template substitution failure) are deterministic and are almost always about declarations, the One Definition Rule, or link order. Runtime memory errors (segfaults, double free, use-after-free) are non-deterministic and should never be debugged by reading code alone; a sanitizer will find in seconds what code review misses for days.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

1. Rebuild with sanitizers before anything else: -fsanitize=address,undefined -fno-omit-frame-pointer -g. AddressSanitizer reports the exact allocation and free sites for use-after-free and double-free.
2. For undefined-reference errors, check link order, remembering that with GNU ld libraries must come after the objects that use them, and check for a C/C++ linkage mismatch that needs extern "C".
3. Use nm -C libfoo.a | grep symbol to confirm the symbol is actually present and to see the demangled signature. A signature that differs by a const is a different symbol.
4. Enable core dumps (ulimit -c unlimited) and open them in gdb with gdb ./binary core, then bt full. A stack trace beats speculation.
5. For template errors, read the message from the bottom up. The final line is usually the real constraint that failed; everything above is instantiation context.

Tools worth reaching for

• -fsanitize=address,undefined
• valgrind
• gdb / lldb
• nm -C
• ldd

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

📖 clang.llvm.org 📖 github.com

Related C++ errors

• C++: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not foundThe binary was built with a newer GCC than the machine it is running on, and it needs a…
• C++: error: 'format' is not a member of 'std'std::format is C++20 and lives in , which needs both the C++20 flag and a recent enough…
• C++: error: 'uint8_t' does not name a typeThe file uses fixed-width integer types without including , and only ever compiled because…
• C++: error: invalid use of incomplete type 'class Foo'The compiler has seen a forward declaration of Foo but not its definition, and this line…
• C++: error: use of deleted functionThe code tries to call a function that has been explicitly deleted, and nine times out of ten…
• C++: pure virtual method called, terminate called without an active exceptionA pure virtual function was called through an object whose derived part does not exist at…
• C++: relocation R_X86_64_32S can not be used when making a shared objectA shared library must be loadable at any address, so every object in it needs position…
• C++: runtime error: signed integer overflow (UBSan)Signed integer overflow is undefined behaviour in C and C++. The program may appear to work…

See all 20 C++ errors →

Browse other categories

• HTTP 494xx client errors, 5xx server errors, redirects, headers and protocol problems.
• JavaScript 42npm resolution, async pitfalls, hydration, memory limits and runtime type…
• Database 41Connections, deadlocks, constraints, replication and memory limits.
• AI 35Rate limits, context windows, GPU memory and model-serving failures.
• Network 35Refused connections, timeouts, resets, MTU problems and port exhaustion.
• Python 35Imports, virtual environments, encoding, concurrency and dependency conflicts.
• Kubernetes 34CrashLoopBackOff, ImagePullBackOff, OOMKilled, RBAC, scheduling and storage.
• Docker 27Daemon connectivity, disk space, image pulls, ports and architecture mismatches.
• System 26Disk space, systemd units, file descriptors, OOM killer and scheduled jobs.
• Cloud 25IAM permissions, quotas, service limits and credential failures.
• Security 25JWT validation, CSRF, OAuth grants, SELinux, SSH host keys and CSP.
• TLS 24Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.