https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #23 from Igor Kushnir <[email protected]> --- (In reply to Matthew Woehlke from comment #22) > What does that have to do with *heap* corruption? And even if the problem > *is* related to a corrupt cache (which it isn't; it's reproducible on a > system running KDevelop for the first time), isn't knowing how file > corruption turns into memory corruption still useful? There may be two different problems: 1. The cache gets corrupted - this is the root cause and should certainly be fixed. 2. A corrupted cache causes a crash - this cannot generally be fixed because the cache is binary and KDevelop assumes it is consistent. KDevelop clears the cache after each minor version update or if a sign of cache corruption is detected. It also offers the user to clear the cache after any crash because the cache *may* be corrupted. KDevelop cannot realistically sanitize any binary corruption and keep the current level of performance. > and, ahem, > maybe you can remind me how to purge the cache first? Run `kdevelop --list-sessions`. Find the session you are testing in the list. Remove the corresponding subdirectory from ~/.cache/kdevduchain/ -- You are receiving this mail because: You are watching all bug changes.
