https://bugs.kde.org/show_bug.cgi?id=361426
--- Comment #17 from Michael Pyne <mp...@kde.org> --- If deleting files were all BleachBit did, that would still be fine. It would make things unnecessarily slower but that's how the existing code clears the cache, it just unlinks the file and lets the kernel do the rest once the shared memory is unmapped. The problem with BleachBit is far more sinister from this POV: it actually mangles the files, filling them with random data, before unlinking them. I can see the appeal, but running it on files in use is a disaster waiting to happen. It's possible that using /dev/shm directly might be workable on the systems we support though, which may at least workaround BleachBit insanity. But I had thought that BleachBit had already removed the KDE cache directory from its default search path? -- You are receiving this mail because: You are watching all bug changes.
