https://bugs.kde.org/show_bug.cgi?id=483684
--- Comment #1 from Arjen Hiemstra <ahiems...@heimr.nl> --- This sounds like it might not have the proper maximum value and thus it ends up just filling the entire area since it doesn't have a range. The next time this happens, can you share the output of "kstatsviewer --details memory/physical/used" and also the same output from when it doesn't happen? -- You are receiving this mail because: You are watching all bug changes.