leakdice-rust

Rust re-implementation of leakdice (by tialaramex)

Leakdice-rust Alternatives

Similar projects and alternatives to leakdice-rust

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better leakdice-rust alternative or higher similarity.

leakdice-rust reviews and mentions

Posts with mentions or reviews of leakdice-rust. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-30.
  • My Rust program (Well, game) is leaking memory, 4MB/s.
    9 projects | /r/rust | 30 Apr 2023
    Maybe try Leakdice: https://github.com/tialaramex/leakdice in C or rewritten in Rust: https://github.com/tialaramex/leakdice-rust/
  • Twenty Years of Valgrind
    6 projects | news.ycombinator.com | 26 Jul 2022
    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
    8 projects | news.ycombinator.com | 15 Oct 2021
    (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
    5 projects | news.ycombinator.com | 18 Jul 2021
  • A note from our sponsor - SaaSHub
    www.saashub.com | 10 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic leakdice-rust repo stats
4
9
0.0
over 2 years ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com