https://bugs.kde.org/show_bug.cgi?id=399601
Bug ID: 399601
Summary: v0.7 - "mark as custom allocator" does not seem to do
anything useful
Product: massif-visualizer
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: massif-visuali...@kde.org
Reporter: a...@weej.com
Target Milestone: 0.4
SUMMARY
In a massif profile I have, we have various C++ "allocate" methods that call
other allocate methods (composed allocators). Unfortunately marking any of
these stack frames as a custom allocator doesn't seem to do anything useful
STEPS TO REPRODUCE
1. Load a profile containing stack traces that have "allocate"-like function
calls
2. Right click such function calls and click "mark as custom allocator"
OBSERVED RESULT
* Item added to custom allocators list, but no change in stack traces
EXPECTED RESULT
* Item added to custom allocators list, and stack traces re-organized to show
actual memory users, not allocators.
SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: n/a
KDE Frameworks Version: n/a
Qt Version:
ADDITIONAL INFORMATION
Running on Ubuntu 18.04, massif-visualizer installed from repo.
Wondering if this is just a user error, or if it seems like a bug I can try to
provide test cases and example massif reports.
Many thanks for your great work!
--
You are receiving this mail because:
You are watching all bug changes.
