bytehound
leakdice-rust
Our great sponsors
bytehound | leakdice-rust | |
---|---|---|
16 | 4 | |
3,856 | 9 | |
- | - | |
3.8 | 0.0 | |
9 months ago | over 2 years ago | |
C | Rust | |
GNU General Public License v3.0 or later | 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.
bytehound
-
My Rust program (Well, game) is leaking memory, 4MB/s.
I've found bytehound helpful for tracking memory leaks: https://github.com/koute/bytehound
-
Show HN: I wrote a tool in Rust for tracking all allocations in a Linux process
Interesting approach. How is performance compared to something like https://github.com/koute/bytehound
-
Introducing alloc-track: Precise memory profiling by stack trace and thread.
https://github.com/koute/bytehound is another tool in this space to be aware of
- Out of the loop: WASM for non-web projects
- Which gui crate would you suggest for a simple program?
-
Implementing a C++ memory allocator to track our framework memory usage
Ot sure if it will fit your needs but maybe bytehound is worth looking into.
-
Memory leak in a long running process.
I had a great success recently with https://github.com/koute/bytehound/issues/86
- 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 ?
- Does rust have a visual analysis tool for memory and performance like pprof of golang?
-
Memory freed but not immediately
Try using this: https://github.com/koute/bytehound
leakdice-rust
-
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
What are some alternatives?
memory-profiler - A memory profiler for Linux. [Moved to: https://github.com/koute/bytehound]
libclang_rt.builtins-wasm32.a - The missing libclang_rt.builtins-wasm32.a file to compile to WebAssembly.
heaptrack - A heap memory profiler for Linux
librdkafka - The Apache Kafka C/C++ library
goawk - A POSIX-compliant AWK interpreter written in Go, with CSV support
mevi - A memory visualizer in Rust (ptrace + userfaultfd)
pprof - pprof is a tool for visualization and analysis of profiling data
Confluent Kafka Golang Client - Confluent's Apache Kafka Golang client
heappy - heap profiler for rust
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
pprof-rs - A Rust CPU profiler implemented with the help of backtrace-rs
jemalloc