Finding memory leaks with Memtrace
Memory issues can be hard to track down. A function that only allocates a few small objects can cause a space leak if it’s called often enough and those objects are never collected. Even then, many…
Read the full article5y ago
You might also wanna read
Exploring Modern Debugger Capabilities for Memory Tracing and Analysis
This doesn't sound like a particularly difficult problem for some scenarios.
news.ycombinator.com·5mo ago
Debugging JavaScript Memory Leaks
Use v8 heap snapshot API + Chrome DevTools to compare heap snapshots
bun.com·1y ago
Building a Rust-Style Static Analyzer for C++ to Prevent Memory Safety Issues
The project is available at
mpaxos.com·6mo ago
Technical Analysis of GrapheneOS's Hardened Malloc Security Allocator
Exploring GrapheneOS secure allocator: Hardened Malloc
synacktiv.com·9mo ago
Discovery of a 64GB Memory Leak in VS Code Despite Never Using the Software
In 2021 I found a huge memory leak in VS code, totalling around 64 GB when I first saw it, but with no actual limit on how high it could go.
randomascii.wordpress.com·9mo ago
Understanding Linux Memory Management: Page Faults, mmap, and userfaultfd
How Linux demand-pages memory, what mmap does to physical pages, why replacing a mapping breaks direct memory access and shared memory, and
shayon.dev·4mo ago
Comments
Sign in to join the conversation.
No comments yet. Be the first.