https://bugs.kde.org/show_bug.cgi?id=361521
--- Comment #12 from David Edmundson <k...@davidedmundson.co.uk> --- Large virtual memory isn't a problem. It can just mean we've mapped a file on disk, even a file that isn't actually that size. We're not using up /any/ resources by doing it. If your resident memory size is high, that's a problem (and the 450Mb is high, that we should identify and fix). Virtual memory being high is pretty much a non issue until proved otherwise. -- You are receiving this mail because: You are watching all bug changes.
