Created attachment 115901 [details] "fake" menu SUMMARY Memory usage increases over time, and latte-dock must be killed to regain it. STEPS TO REPRODUCE 1. Just having the plasmoid active OBSERVED RESULT Latte-dock's process memory consumption increases indefinitely, but this only happens with active window control's plasmoid is active. EXPECTED RESULT No memory leak SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION the programs I use regularly that integrate well with AWC are dolphin and konsole, I don't have a patched firefox, so it shows no menu, same with steam, however, I use glowing bear, which is an electron program which has a menu, this menu can't be interacted (clicking them doesn't do anything, it doesn't show the items of the supposed menus either) with the entries: edit, view, window, help. What's more, if I switch from glowing bear to firefox, steam or any other program which has no menu, they will show the same non-interactive menu as glowing bear, this will happen until I change to an application that has a menu (like konsole and dolphin) and until I switch to glowing bear again. I don't know if this is or isn't part of the ram problem, but I'm listing it just in case. The applications I use regularly are: firefox-nightly, konsole, dolphin, gmusicbrowser, lutris, steam, feedreader, kate and glowing bear.
Ok, so following in the reported menu oddity, I decided to not launch glowing-bear at all, and the memory usage has not increased, so something regarding it is causing the memory leak in AWC. When I'm able I'll update glowing-bear and see if this still happens with current master, but I'm currently using glowing bear 0.6.0 (gf47043f)
After updating glowing bear to the version 0.8.0 the menu can be interacted with, and there's no more "ghost" menu being passed to menu-less applications, and the memory consumption stopped increasing. It's probably unlikely to encounter this bug on the wild (it's probably bound to some older version of electron), but it might be a good idea to investigate it when devs have the time as who knows if it might also trigger under different conditions.