Summary: | ksysguard leaking some memory | ||
---|---|---|---|
Product: | [Unmaintained] ksysguard | Reporter: | Ömer Fadıl USTA <omerusta> |
Component: | libksysguard | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | bugseforuns, euphonisten, mnmm1j+4hehta00jreko, plasma-bugs, quantumphazor |
Priority: | NOR | ||
Version: | 5.19.90 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Valgrind log |
Description
Ömer Fadıl USTA
2020-09-21 05:33:05 UTC
Created attachment 131820 [details]
Valgrind log
Still a problem in 5.20.0 Also a problem for the systemmonitor (System Activity) spawned from Ctrl+Esc Leaving them both open overnight can lead to over 1 GiB of usage. Current usage after leaving it on overnight: ksysguard: 1.9 G systemmonitor: 1.4 G Same story for me: Plasma 5.20.1 Frameworks 5.75.0 Qt 5.15.1 Memory used by KSysGuard will steadily increase and can reach 2GiB overnight. Also note https://bugs.kde.org/show_bug.cgi?id=428048 as a possible duplicate of this bug. https://github.com/KDE/libksysguard/commit/23852597c642a5c5303bb994d4d28e20d9c863cb will not compile for me with "error: ‘Updates’ in ‘class KSysGuard::Process’ does not name a type" - like errors https://github.com/KDE/libksysguard/commit/40cb8d6acbb12e516c1d327a9b2574560adcb4ec is Ok for me,later commits have KSysGuard run away with my memory *** This bug has been marked as a duplicate of bug 428048 *** |