https://bugs.kde.org/show_bug.cgi?id=423372
--- Comment #4 from vindicator <nroycea+...@gmail.com> --- Created attachment 129634 --> https://bugs.kde.org/attachment.cgi?id=129634&action=edit Memory Usage Chart Stuck For "Available". Uptime Is Always "0.0" Okay, this time I opted to let it go for over 24 hours. I ended it when it was ~1.4GB. When things looked steady/healthy WITHOUT the widgets, I re-added them ~5.5 hours later, where it looked to have increased comparatively slowly. Heaptrack also confirms libQuickCharts.so as being the largest holder of memory. Let me know if you still want the .zst file. It's 241MB. I've also attached a screenshot of my widget setup because there are a few issues. Let me know if you want me to make another bug(s) for them... Basically 1) the "Ava[i]lable"[sic] "Memory Usage" line isn't moving. At some point, it just stops. 2) Long names cut off. It would be nice to allow the user to customize the data field names like "/home read speed" instead of "Read data device dm..." which got cut off 3) "System uptime" always shows as 0.0. 4) (not in screenshot) There are 2 "Uptime" "sensors". First is the lone sensor in the list of folder/categories when you go to the "Sensors Details". The second is when you go under the "System->Uptime" category which is labeled as "System uptime" which also shows as 0.00. -- You are receiving this mail because: You are watching all bug changes.
