KLklaussilveira·May 23, 2024Submission
Bytehound: Memory Profiler for Linux
167 points · Open discussionkoute
bytehound
C2019–2024
koute / bytehound
bytehound
A memory profiler for Linux.
7Distinct people
8Mentions
0Explicit recommenders
4.8KGitHub stars
What to know before exploring
What it is
A memory profiler for Linux.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year8 dated mentions
Observed mentions: 2019-05-19 02:31:13 UTC to 2024-05-23 14:40:58 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
8 sources> do we really still not have a decent memory usage analysis tool for c/ C++ ?
Shameless plug: not sure if I'd call it decent, but you might want to check my Bytehound for more in-depth analysis:
https://github.com/koute/bytehound
In Memory Profiling: IntroductionInteresting approach. How is performance compared to something like https://github.com/koute/bytehound
In Show HN: I wrote a tool in Rust for tracking all allocations in a Linux process> Once you’re calling malloc/free hundreds of thousands of times a second the overheard of jumping into the kernel every time cripples performance.
Shameless plug in case you (or anyone else) is interested, I wrote a memory profiler for exactly this usecase:
https://github.com/koute/bytehound
It's definitely not perfect, but it's relatively fast, has an okay-ish GUI, and it's even scriptable: https://koute.github.io/bytehound/memory_leak_analysis.html
In Hunting down a C memory leak in a Go programHmm, took a look (it's called Bytehound now), it has no PKGBUILD nor a `cargo install` crate so I can't install it in systemwide or user PATH, and requires Yarn to download and build JS dependencies (likely hundreds or thousands).
I tried `cargo install --git https://github.com/koute/bytehound.git`, but that results in "error: multiple packages with binaries found: bytehound-cli, bytehound-gather, interrupt, linking, lz4-compress, simulation".
For the time being I'll stick with heaptrack.
In Go 1.17 Release NotesBytehound: A Memory Profiler for Linux
4 points · Open discussionA new memory profiler for Linux written in Rust
212 points · Open discussionNew Linux Memory Profiler from Nokia
8 points · Open discussion