| Summary: | Plasma crash while removing cache files | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kcoreaddons | Reporter: | Joseph Guida <joe85255> |
| Component: | general | Assignee: | Michael Pyne <mpyne> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | aleixpol, kdelibs-bugs-null, notmart |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | attachment-19889-0.html | ||
|
Description
Joseph Guida
2016-02-01 20:08:10 UTC
seems some symbols for KSharedDataCache are missing possible thread unsafety of kshareddatacache? Bleachbit overwrites the cache instead of simply unlinking it, which is what causes the crash. There's not much I can do here because the cache is persistent so it must save its accounting data within the file itself, which Bleachbit then corrupts, leading to crashes almost instantly. This type of bug has been reported before, my understanding was that the Bleachbit devs had configured the software to leave things like /var/tmp/kdecache* alone by default but I'm not sure (and I'm sure it's still possible for user to override). See Martin's blog post from nearly 4 years ago now to see how long this has been going on https://blog.martin-graesslin.com/blog/2012/07/do-not-use-bleachbit/ Created attachment 97348 [details] attachment-19889-0.html Thank you much for the information about Bleachbit's causation of this crash. I will cease using it. Your reply is very much appreciated. Joe G On Feb 19, 2016 9:39 PM, "Michael Pyne via KDE Bugzilla" < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=358887 > > Michael Pyne <mpyne@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|NEEDSINFO |RESOLVED > Resolution|BACKTRACE |INVALID > > --- Comment #3 from Michael Pyne <mpyne@kde.org> --- > Bleachbit overwrites the cache instead of simply unlinking it, which is > what > causes the crash. There's not much I can do here because the cache is > persistent so it must save its accounting data within the file itself, > which > Bleachbit then corrupts, leading to crashes almost instantly. > > This type of bug has been reported before, my understanding was that the > Bleachbit devs had configured the software to leave things like > /var/tmp/kdecache* alone by default but I'm not sure (and I'm sure it's > still > possible for user to override). See Martin's blog post from nearly 4 years > ago > now to see how long this has been going on > https://blog.martin-graesslin.com/blog/2012/07/do-not-use-bleachbit/ > > -- > You are receiving this mail because: > You reported the bug. > |