| Summary: | Crash Swiching to "Simple Menu" launcher. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Tony <jodr666> |
| Component: | generic-crash | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | abenson, notmart, oysstu |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Tony
2017-02-21 07:43:59 UTC
this backtrace says that a frameData was deleted but not removed correctly from the hash. I tried to reproduce it by creating and destroying a lot of frames of random sizes, but i don't seem to be able to reproduce it, the framedata that gets deleted seems to be always correctly removed from the hash (In reply to Marco Martin from comment #1) > this backtrace says that a frameData was deleted but not removed correctly > from the hash. > I tried to reproduce it by creating and destroying a lot of frames of random > sizes, but i don't seem to be able to reproduce it, the framedata that gets > deleted seems to be always correctly removed from the hash Can it possibly be a driver issue? Git commit 2b3e8dfe866abc5b2971eecb4c52843e73be1893 by Marco Martin. Committed on 28/02/2017 at 12:35. Pushed by mart into branch 'master'. move setImagePath logic into updateFrameData() Summary: make sure the framedata creation/destruction is completely in updateFrameData, makes easier to track and possible to use the repaintsblocked logic. now only one framedata instance should be created at startup. Test Plan: * autotests pass, plasma runs ok, crash on 376754 not reproducible anymore * possible to have a plasmashell session start without the creation of a single svg renderer (startups after the first when the cache is generated) * on qml profiler, framesvgitem creation is ~12 msecs the first one created, ~2-300 musecs the subsequent ones, seems to be a bit better than before the whole refactor started * tried against the latest patches that remove the binding loops, still correct rendering and no binding loop * tried with both empty and existing cache in place Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: davidedmundson, plasma-devel, #frameworks Tags: #frameworks, #plasma Differential Revision: https://phabricator.kde.org/D4707 M +78 -88 src/plasma/framesvg.cpp M +5 -2 src/plasma/private/framesvg_p.h M +2 -3 src/plasma/svg.cpp https://commits.kde.org/plasma-framework/2b3e8dfe866abc5b2971eecb4c52843e73be1893 the part interested by the crash is changed by klast commit. if still happens open a new one *** Bug 270915 has been marked as a duplicate of this bug. *** *** Bug 381685 has been marked as a duplicate of this bug. *** |