https://bugs.kde.org/show_bug.cgi?id=436900
Grzesiek11 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REPORTED Resolution|FIXED |--- --- Comment #3 from Grzesiek11 <[email protected]> --- It's not fixed. Turns out a lot of waiting isn't guaranteed to trigger this issue. Here is the Valgrind report: https://grzesiek11.stary.pc.pl/files/texts/436900_valgrind.log (~80 MiB, be warned). I have no idea if I had done this right, I just copy-pasted the command found on the Wiki ('valgrind --leak-check=full --show-reachable=yes --track-origins=yes --trace-children=yes --log-file=plasmashell.log plasmashell') and left it overnight. plasmashell became very slow and unresponsive (which I guess is how Valgrind works), so I didn't use it at all and started everything from Konsole (that was not started by plasmashell, so it wouldn't be it's child). I don't know if I reproduced the issue, since Valgrind replaces the plasmashell process and it used 1.1 GiB at start (it grew to 1.7 GiB when I stopped it). -- You are receiving this mail because: You are watching all bug changes.
