https://bugs.kde.org/show_bug.cgi?id=432449
--- Comment #13 from Fabian Otto <fabian_otto...@yahoo.de> --- (In reply to David Edmundson from comment #11) > Framegraph shows two distinct areas of usage at peak: > - Appstream (150Mb) > - Your graphic drivers (300Mb) > > Neither of which seem ideal. > > > Can you confirm that krunner also spirals out of control after doing a query? > and if you get high usage in systemsettings5 I can confirm, that krunner too also starts to memleak after doing a query. Heaptrackfile for it here: https://mega.nz/file/cPxEiY4S#zWyWEXuuxAZ0m48b-ErL0ub2lG239skJWjgBef23RyU ``` total runtime: 74.23s. calls to allocation functions: 8103421 (109173/s) temporary memory allocations: 539318 (7265/s) peak heap memory consumption: 101.37MB peak RSS (including heaptrack overhead): 272.14MB total memory leaked: 98.78MB ``` As for systemsettings5 I do not get high resource usage here. Neither in RAM nor CPU. -- You are receiving this mail because: You are watching all bug changes.
