Bug 377339

Summary:	Make it possible to create a flamegraph at the time of peak memory usage
Product:	[Applications] Heaptrack	Reporter:	Teodor Petrov <fuscated>
Component:	general	Assignee:	Milian Wolff <mail>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:	https://commits.kde.org/heaptrack/fc6c6be2d8803d194d31fddb326cae54018aa54e	Version Fixed/Implemented In:
Sentry Crash Report:

Description Teodor Petrov 2017-03-07 16:31:34 UTC

I'm using heaptrack_print to create flamegraphs.
What I need is to see all allocations that are active (non-freed) at the time of peak memory usage. This way I can see what is contributing to the memory usage of my application and thus try to improve it.

At the moment I see total number of allocations per call-path for the whole run of my application.

Comment 1 Milian Wolff 2018-03-21 16:49:24 UTC

Git commit fc6c6be2d8803d194d31fddb326cae54018aa54e by Milian Wolff.
Committed on 21/03/2018 at 16:47.
Pushed by mwolff into branch 'master'.

Add --flamegraph-cost-type to heaptrack_print

This allows specifying the cost type to print when generating
the flamegraph. All available cost types can be used, i.e.:

- allocations (still the default)
- temporary
- allocated
- leaked
- peak

M  +55   -1    src/analyze/print/heaptrack_print.cpp

https://commits.kde.org/heaptrack/fc6c6be2d8803d194d31fddb326cae54018aa54e