https://bugs.kde.org/show_bug.cgi?id=480739
--- Comment #9 from Milian Wolff ---
sure, I can try to improve the documentation.
but I guess the real question is: what problem did you have when you didn't
pass that along? worst case it will fail to launch the `heaptrack_gui` after
analysis is
https://bugs.kde.org/show_bug.cgi?id=480739
Arvid Norlander changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=480739
--- Comment #7 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=480739
--- Comment #6 from Arvid Norlander ---
Thanks for your feedback. I'll take a look later today or tomorrow.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480739
Milian Wolff changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=480739
--- Comment #4 from Milian Wolff ---
oh I now see your attempt at using the tool. it seems to assume .gz input - can
you replace the zcat with zstdcat and rerun?
also: you cannot directly analyze a raw trace, you first need to interpret that
with
https://bugs.kde.org/show_bug.cgi?id=480739
--- Comment #3 from Milian Wolff ---
can you either send me the original heaptrack file you analyze to trigger the
crash (to my email address), or run it through the `heaptrack/tools/anonymize`
tool and then send it to me?
that way I can better figure
https://bugs.kde.org/show_bug.cgi?id=480739
--- Comment #2 from Arvid Norlander ---
As a workaround for anyone else who runs into this issue: You can capture a
trace with https://github.com/koute/bytehound then export that trace to a
heaptrack trace, which can then be loaded into the
https://bugs.kde.org/show_bug.cgi?id=480739
--- Comment #1 from Arvid Norlander ---
By the way, if I attach to the program everything works fine. Unfortunately I
want to investigate the memory usage during the startup phase of the program,
so that is not very useful to me.
--
You are receiving
