Bug 515657 - Kwin leaks memory when loading audio files in Audacity
Summary: Kwin leaks memory when loading audio files in Audacity
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: kwin
Classification: Plasma
Component: performance (other bugs)
Version First Reported In: 6.5.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-06 21:31 UTC by thesword
Modified: 2026-02-09 18:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thesword 2026-02-06 21:31:21 UTC
SUMMARY

Each time I open an audio file in Audacity, the memory usage of Kwin increases and is never freed even if I close Audacity. I also observe hitches when I change the accent color or the theme. Freeze duration is proportional to amount of leaked memory.

I already opened an issue to the Klassy theme project thinking that the issue was coming from there. (https://github.com/paulmcauley/klassy/issues/260). But the memory leak also happens with the Breeze theme and Klassy removed from the system and is way worse with the Plastik windows decorations.
I also opened this bug previously (https://bugs.kde.org/show_bug.cgi?id=514810).

STEPS TO REPRODUCE
1. Open a file explorer in a directory with audio files
2. Open Audacity
3. Drag the audio file from the file explorer to Audacity and undo with Ctrl+Z
4. Repeat the step 3 multiple times, and see memory usage of kwin.

OBSERVED RESULT
Memory usage of kwin increases

EXPECTED RESULT
Memory usage of kwin doesn't increase

SOFTWARE/OS VERSIONS
Linux Version: 6.18.7.arch1-1
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.2
Audacity Version: 3.7.7
Comment 1 Harald Sitter 2026-02-09 15:26:48 UTC
Does this happen with a newly created users, without any modifications?
Comment 2 thesword 2026-02-09 18:33:56 UTC
Yes. I reproduced the issue on 2 different PC and a virtual machine.