Created attachment 115810 [details] Consumption after 2 and a half hours of being launched SUMMARY After being open for a few hours latte-dock starts consuming upwards to 800mb of ram (and possibly more if left open for longer time), this happens even when using an unmodified unity layout (except for changing icon size of currently open applications). STEPS TO REPRODUCE 1. Launch latte-dock 2. Wait a few hours (time varies) OBSERVED RESULT Ram usage increases over time, seemingly a memory leak. 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 I've observed this memory leak problem since 0.7.x, but at the time I didn't test with a default layout, so it's possible the problem at the time might have been due to one of my plasmoids.
1. what is your memory size? 2. Please try also with the Default layout, that is the layout that contains only one dock with Latte taskmanager in it and an analog clock
1. 8gb, and latte dock has gotten to consume up to half of my ram given enough open time. 2. I'll try, I'll report back when sufficient time has passed.
Memory usage has remained solidly at 180mb (including shared memory), so just speaking my mind I can think of the following possible reason: - Problem in how latte handles a number of plasmoids, panels or a combination of both (probably not the case). - One of the plasmoids is the problem. Going by the second route one should compare the default layout with unity, and unity, beside having a second panel, also has a digital clock, the system tray, an user switcher, an application launcher, and two instances of active window control (if there was anything else then I removed it and has no bearing in the memory problem). I'd say most of these are ubiquitous, and so I consider that the most likely culprit would be the active window control applet. There doesn't appear to have been much change in their repo since last time I built it, but I'll still make sure to be current with master before further testing. First using it normally with unity layout as I was doing before, and, if the problem continues, test without active window control in particular.
After some testing, it seems that the root of the memory leak is active window control. With unity layout, but without that plasmoid, latte's memory consumption went up to 280mb (including shared memory), but goes much further (over 800mb after several hours, and was still increasing until the process was killed) with active window control. So, what's the proper way to proceed? should I just change title and product category of the bug?
Close this and create a new one for AWC.
Nice