Summary: | Plasma frequently crashes with new installation | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | webegood |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bhush94, nowrep, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.4.3 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/plasma-framework/a8e54e15e13653290ca4a49a38fae742e3825d04 | Version Fixed In: | |
Sentry Crash Report: |
Description
webegood
2016-02-18 14:55:33 UTC
I can't reproduce it, but I think I can see how this can happen. The issue is that KSharedConfig is created and removed on different thread, which it can't handle (it holds raw pointers in per-thread storage). It gets created on scene graph thread (as seen from backtrace), but then may be removed from main thread (from ThemePrivate::notifyOfChanged slot). So is plasma-framework using it incorrectly, or should KSharedConfig handle this case? Can you try this patch https://git.reviewboard.kde.org/r/127112/ ? Git commit a8e54e15e13653290ca4a49a38fae742e3825d04 by David Rosca. Committed on 19/02/2016 at 12:25. Pushed by drosca into branch 'master'. Reparse svgElementsCache instead of deleting it in discardCache svgElementsCache may be created on render thread and deleted on main thread, which will make KSharedConfig crash because it uses per-thread storage. REVIEW: 127112 M +1 -1 src/plasma/private/theme_p.cpp http://commits.kde.org/plasma-framework/a8e54e15e13653290ca4a49a38fae742e3825d04 |