heaptrack
leakdice
heaptrack | leakdice | |
---|---|---|
19 | 4 | |
3,021 | 18 | |
1.8% | - | |
8.9 | 0.0 | |
12 days ago | about 5 years ago | |
C++ | C | |
GNU Lesser General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
heaptrack
-
Tracking Java Native Memory with JDK Flight Recorder
If we are talking replacing the libc allocator, then something like heaptrack is worth mentioning.
https://github.com/KDE/heaptrack
- Ask HN: Are There Viewers for Memory Layout?
-
How to Perf profile functions?
For accurate memory usage I prefer a memory profiler that overrides malloc and friends instead of the ones that probe the OS at regular intervals. You won't find memory spikes with the latter. Try heaptrack on Linux. I haven't found a good one for Windows yet.
-
What is your favourite profiling tool for C++?
I know it is not a profiler, but it is so criminally underrated that I decided to share it: https://github.com/KDE/heaptrack
-
My Rust program (Well, game) is leaking memory, 4MB/s.
If none of the above helps - I recommend heaptrack as a tool for tracking down your memory usage.
-
Lessons learned from 15 years of SumatraPDF, an open source Windows app
> memory leaks. It's surprisingly hard to find an easy to use memory leak detection tool.
I can vouch for heaptrack[1] nowadays, although it's pretty much Linux only. It's under the umbrella of KDE, but a heaptrack trace only requires a CLI app, and there is a nice Qt viewer to analyse the memory consumption.
It tracks the memory utilization at the level of malloc'd/free'd bytes. It's fine if your memory leak or other memory utilization problem is on this level. Recently I dealt with an issue, where increasing memory utilization was caused by fragmentation within the allocator. This didn't show up in heaptrack as an increasing memory utilization, but heaptrack still pointed out where most of the temporary allocations happened, leading to the culprit of the fragmentation.
[1] https://github.com/KDE/heaptrack
- Show HN: I wrote a tool in Rust for tracking all allocations in a Linux process
-
Implementing a C++ memory allocator to track our framework memory usage
This is probably what you are looking for https://github.com/KDE/heaptrack
-
Memory Leak? Free memory not being reclaimed? What is happening here
When I had this kind problems (heap related) I always use heaptrack. Take a look here for the details: https://github.com/KDE/heaptrack
- Hi, I’m new in rust, I have some expirience with c# and its classes ans structs. I can’t find information about that is happend with struct in rust when I pass it to function argument. Are there some copy effect ?
leakdice
-
My Rust program (Well, game) is leaking memory, 4MB/s.
Maybe try Leakdice: https://github.com/tialaramex/leakdice in C or rewritten in Rust: https://github.com/tialaramex/leakdice-rust/
-
Twenty Years of Valgrind
In my obviously biased opinion, very specialised, but sometimes exactly what you needed (I have used this in anger maybe 2-3 times in my career since then, which is why I wrote the C version):
https://github.com/tialaramex/leakdice (or https://github.com/tialaramex/leakdice-rust)
Leakdice implements some of Raymond Chen's "The poor man’s way of identifying memory leaks" for you. On Linux at least.
https://bytepointer.com/resources/old_new_thing/20050815_224...
All leakdice does is: You pick a running process which you own, leakdice picks a random heap page belonging to that process and shows you that page as hex + ASCII.
The Raymond Chen article explains why you might ever want to do this.
-
Hunting down a C memory leak in a Go program
(or there's a Rust rewrite https://github.com/tialaramex/leakdice-rust because I was learning Rust)
leakdice is not a clever, sophisticated tool like valgrind, or eBPF programming, but that's fine because this isn't a subtle problem - it's very blatant - and running leakdice takes seconds so if it wasn't helpful you've lost very little time.
Here's what leakdice does: It picks a random heap page of a running process, which you suspect is leaking, and it displays that page as ASCII + hex.
That's all, and that might seem completely useless, unless you either read Raymond Chen's "The Old New Thing" or you paid attention in statistics class.
Because your program is leaking so badly the vast majority of heap pages (leakdice counts any pages which are writable and anonymous) are leaked. Any random heap page, therefore, is probably leaked. Now, if that page is full of zero bytes you don't learn very much, it's just leaking blank pages, hard to diagnose. But most often you're leaking (as was happening here) something with structure, and very often sort of engineer assigned investigating a leak can look at a 4kbyte page of structure and go "Oh, I know what that is" from staring at the output in hex + ASCII.
This isn't a silver bullet, but it's very easy and you can try it in like an hour (not days, or a week) including writing up something like "Alas the leaked pages are empty" which isn't a solution but certainly clarifies future results.
-
`Zig Cc`: A Powerful Drop-In Replacement for GCC/Clang
Right. Even in an entirely safe language you can have leaks, and valgrind is an effective way to find those leaks if you can afford the virtualisation overhead.
If you can't afford the virtualisation overhead, and you need to find leaks you should try what Raymond Chen suggests in "The poor man's way of identifying memory leaks" (not bothering to link since Microsoft will only move it anyway, they have several times since I read it). If you are too lazy to do it by hand, or find the technique works but wish it less manual, this is what Leakdice does:
https://github.com/tialaramex/leakdice
What are some alternatives?
bytehound - A memory profiler for Linux.
libclang_rt.builtins-wasm32.a - The missing libclang_rt.builtins-wasm32.a file to compile to WebAssembly.
memory-profiler - A memory profiler for Linux. [Moved to: https://github.com/koute/bytehound]
mevi - A memory visualizer in Rust (ptrace + userfaultfd)
dhat-rs - Heap profiling and ad hoc profiling for Rust programs.
flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3
hotspot - The Linux perf GUI for performance analysis.
pprof - pprof is a tool for visualization and analysis of profiling data
Confluent Kafka Golang Client - Confluent's Apache Kafka Golang client
profiler - Firefox Profiler — Web app for Firefox performance analysis
librdkafka - The Apache Kafka C/C++ library