Summary: | Plasma crashed after closing Google Chrome | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Edward Nygma <Enygma2002_ro> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | justin.zobel, notmart, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.11.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Edward Nygma
2018-02-01 18:17:34 UTC
even tough symbols aren't completed, it can be deduced that on plasma side the crash is at iconitem.cpp line 233 if (width() > 0 && height() > 0) { schedulePixmapUpdate(); } (which in turn calls polish() which I don't understand much why it crashes, i would guess that item is in tearing down process but hasn't been deleted yet from the implementation of QQuickITem::polish() maybe d->window is a dangling pointer? void QQuickItem::polish() { Q_D(QQuickItem); if (!d->polishScheduled) { d->polishScheduled = true; if (d->window) { QQuickWindowPrivate *p = QQuickWindowPrivate::get(d->window); bool maybeupdate = p->itemsToPolish.isEmpty(); p->itemsToPolish.append(this); if (maybeupdate) d->window->maybeUpdate(); } } } Can you try to reproduce with qtQuick debug symbols installed? Sorry, but I can't really reproduce it by just starting and closing Chrome. Most likely there were other factors involved that I did not notice to record. Thank you for the report, Edward. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |