https://bugs.kde.org/show_bug.cgi?id=509180
--- Comment #15 from [email protected] --- (In reply to guimarcalsilva from comment #14) > Created attachment 186353 [details] > Heaptrack screenshot > > I decided to take a look at the file. I don't have the technical expertise > to understand exactly what's happening, but apparently some kind of XML > parser is (one of) the culprits for the huge memory consumption. Now, the > question that stands is: Why does discover-notifier needs to parse so much > data (from the package metadata?) just to show the number of available > updates? Could there be a cheaper way to show how many updates are available? Also, even if that process is needed, couldn't it unload that data at some point when it's not needed anymore? -- You are receiving this mail because: You are watching all bug changes.
