allocscope
heaptrack
allocscope | heaptrack | |
---|---|---|
4 | 19 | |
544 | 3,037 | |
- | 2.3% | |
2.3 | 8.9 | |
about 1 year ago | 5 days ago | |
Rust | C++ | |
GNU General Public License v3.0 only | GNU Lesser 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.
allocscope
- A memory tracking tool written in Rust
- Show HN: I wrote a tool in Rust for tracking all allocations in a Linux process
-
Announcing allocscope: a tool for tracking allocations in Rust / C++ / C apps
It is now available, with complete GNU GPL v3 source code (written in Rust) on github at https://github.com/matt-kimball/allocscope
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 ?