KWin running away with memory usage

[egerlach]

I'm on Aurora Stable. Over the last week or so sometimes I've come back to my machine and the KDE session will be starting from scratch. I've been feeling gaslit because I didn't remember logging out.

Today, I caught kwin_wayland with Virtual Memory usage of over 130GB, with more than 50GB resident. I almost got a picture of htop on my screen as my system was slowing down due to starting to thrash, but KWin got oom-killed before I could snap it and the session restarted.

Is anyone else running into this? Anything I can do to try to capture more info next time it happens to help devs? Should I be asking about this here? discuss.kde.org?

If it hadn't happened multiple times recently, I wouldn't be writing this.

Investigation so far:

Looking in the journal, I see the OOM killer going nuts on a few other processes before deciding to nuke kwin_wayland. When the first oom-killer happened, the kernel dumped the full task state (highly abridged, via journalctl -S today -u kernel):

May 06 11:20:47 egerlach-desktop kernel: [  pid  ]   uid  tgid total_vm      rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name
May 06 11:20:47 egerlach-desktop kernel: [ 474921]  1000 474921 35364389 14387807 14372196      173     15438 277381120 20055452           200 kwin_wayland

There were other things that had big total_vm numbers, but nothing that had that much resident.

There's a bunch of other mess in the journal, but prior to the OOM kills nothing much seems relevant. There's no evidence of the RAM usage going up in the logs until less than a minute before the OOM killer kicked in.

[egerlach]

I managed to catch it before it killed itself today, and it turns out that it is Betterbird that is somehow causing bloat of kwin.

If anyone has any tips on how to get more info on where that might be coming from, I'm all ears. I'll take it to the KDE discuss too as they will probably have better knowledge.

[renner0e]

If you have a reliable way of reproducing it then you want to file a bug report on https://bugs.kde.org