https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #147 from LucasGGamerM <lucasggam...@protonmail.com> --- (In reply to TraceyC from comment #146) > (In reply to LucasGGamerM from comment #144) > > I have ran the instructions provided by TraceyC, and so far, with 3.8 gigs > > leaked, here is the "sudo perf report" output, I hope it is useful. > > Thank you for providing that. This report is set to high priority, so > hopefully one of the KWin developers can take a further look at this in the > near future. One thing of notice that my copy and paste did not include, and that I just noticed through putting both the normal kwin stack and the leaking kwin stack side by side in flamegraph was that the leaky kwin had a lot more "blocks" in their flamegraph graph. What I mean is that the stack in the leaky kwin is around 20-30 times bigger in terms of filesize when compared to a normal kwin stack, and it also looked like every function had made a bunch of instances of itself over and over again. I can share the graphs and the stack trace if requested, I tried sharing directly in a comment, but I think files are not allowed. -- You are receiving this mail because: You are watching all bug changes.
