https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #15 from Anthony Fieroni ---
Furthermore i mount my ~/.cache folder as tmpfs which can lead in much ram
consumption, but it's intersting to me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #14 from Anthony Fieroni ---
I *really* should make new trace but even with this i can speculate over
plasma' theme cache.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392085
Milian Wolff changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/hea
|
https://bugs.kde.org/show_bug.cgi?id=392085
Milian Wolff changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/hea
|
https://bugs.kde.org/show_bug.cgi?id=392085
Milian Wolff changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #10 from Milian Wolff ---
I cannot open it with the GUI, it also goes through all of my memory and then
dies. But I can open it with `heaptrack_print`, which doesn't implement the
full algorithm to merge backtraces. Thus it doesn't require t
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #9 from Milian Wolff ---
Git commit e253b08794c62a14c6a521c6f08a5721e7dffd1c by Milian Wolff.
Committed on 22/04/2018 at 07:38.
Pushed by mwolff into branch 'master'.
Mark files with duplicated debuggee entries as corrupt
Since we do not (
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #8 from Anthony Fieroni ---
Please explain what you see and why it shouldn't be possible?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #7 from Anthony Fieroni ---
Slow down, can you open the file?
I'm starting it in bin folder (as describe in first comment)
./heaptrack -d plasmashell
Distribution is KaOS
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #6 from Milian Wolff ---
What distribution and version are you using? How did you invoke heaptrack
exactly? I cannot reproduce at all what you are seeing...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #5 from Milian Wolff ---
Reproduced with the latest file you attached. Inspecting the backtraces with
`heaptrack_print` shows they are completely fubared. Just to double check, can
you tell me the output of `git describe`? And you are sure y
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #4 from Anthony Fieroni ---
Update to master - still it's killed
https://drive.google.com/open?id=1TXAgA-PGs_KBVNuenIqQcohcwfX032mK
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #3 from Milian Wolff ---
please attach the file, and with "wait 1-2min" you mean while tracking
plasmashell with heaptrack?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #2 from Anthony Fieroni ---
So you can wait 1~2 min or i can attach my file.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392085
--- Comment #1 from Milian Wolff ---
please attach the file your get.
I tested your steps - it consumes ~1.5GB for me, but it doesn't die.
--
You are receiving this mail because:
You are watching all bug changes.
15 matches
Mail list logo
