[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 Nate Graham changed: What|Removed |Added Version Fixed In||5.27 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 Arjen Hiemstra changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-systemmonitor/com |ma/plasma-systemmonitor/com |mit/ebd169763aea87fa6203dc8 |mit/d8dc56057758a50b23c4a23 |f12ced639428525f4 |521fbf534daf61e28 --- Comment #10 from Arjen Hiemstra --- Git commit d8dc56057758a50b23c4a23521fbf534daf61e28 by Arjen Hiemstra. Committed on 26/01/2023 at 14:16. Pushed by ahiemstra into branch 'Plasma/5.27'. table: Workaround a memory leak in QQmlPropertyCache Apparently, the combination of a Connections object along with the QAbstractItemModel::layoutChanged() signal leads to a memory leak inside QQmlPropertyCache::createArgumentsObject(). To avoid that, put a proxy signal in between that Connections can connect to. The bug no longer exists in Qt 6 so this should be reverted after switching to Qt 6. (cherry picked from commit ebd169763aea87fa6203dc8f12ced639428525f4) M +2-0 src/faces/applicationstable/contents/ui/ApplicationsTableView.qml M +2-0src/faces/processtable/contents/ui/ProcessTableView.qml M +2-2src/table/BaseCellDelegate.qml M +14 -0src/table/BaseTableView.qml https://invent.kde.org/plasma/plasma-systemmonitor/commit/d8dc56057758a50b23c4a23521fbf534daf61e28 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 Arjen Hiemstra changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-systemmonitor/com ||mit/ebd169763aea87fa6203dc8 ||f12ced639428525f4 Resolution|--- |FIXED --- Comment #9 from Arjen Hiemstra --- Git commit ebd169763aea87fa6203dc8f12ced639428525f4 by Arjen Hiemstra. Committed on 26/01/2023 at 13:57. Pushed by ahiemstra into branch 'master'. table: Workaround a memory leak in QQmlPropertyCache Apparently, the combination of a Connections object along with the QAbstractItemModel::layoutChanged() signal leads to a memory leak inside QQmlPropertyCache::createArgumentsObject(). To avoid that, put a proxy signal in between that Connections can connect to. The bug no longer exists in Qt 6 so this should be reverted after switching to Qt 6. M +2-0 src/faces/applicationstable/contents/ui/ApplicationsTableView.qml M +2-0src/faces/processtable/contents/ui/ProcessTableView.qml M +2-2src/table/BaseCellDelegate.qml M +14 -0src/table/BaseTableView.qml https://invent.kde.org/plasma/plasma-systemmonitor/commit/ebd169763aea87fa6203dc8f12ced639428525f4 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 --- Comment #8 from Onyx --- Created attachment 154015 --> https://bugs.kde.org/attachment.cgi?id=154015=edit A little later and still climbing, no suspend yet. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 --- Comment #7 from Onyx --- Created attachment 154012 --> https://bugs.kde.org/attachment.cgi?id=154012=edit Current Started at 137mb, gradual creep through the day. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 --- Comment #6 from Onyx --- (In reply to Arjen Hiemstra from comment #5) > So this only happens when running it for a long time? Or does it always > happen after resuming from suspend? Always after a long time for me. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 --- Comment #5 from Arjen Hiemstra --- So this only happens when running it for a long time? Or does it always happen after resuming from suspend? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 --- Comment #4 from Riccardo Robecchi --- *** Bug 460561 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 Riccardo Robecchi changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Riccardo Robecchi --- It started leaking again on 5.26.0 for me as well, after a few days in which it stayed at a very low memory footprint (< 100 MB). Since this affects at least another user, I am marking this as "confirmed". -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 Onyx changed: What|Removed |Added CC||onyx...@gmail.com --- Comment #2 from Onyx --- Created attachment 152963 --> https://bugs.kde.org/attachment.cgi?id=152963=edit Screenshot version 5.26.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460370] System Monitor leaks memory
https://bugs.kde.org/show_bug.cgi?id=460370 --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! Please note that Plasma 5.25.5 is not supported for much longer by KDE; supported versions are 5.24, and 5.26 or newer. If at all possible please upgrade to a supported version and verify that the bug is still happening there. -- You are receiving this mail because: You are watching all bug changes.
