| Summary: | KDevelop late crash on exit (ContextBrowser UI access during global destruction?) | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | RJVB <rjvbertin> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version First Reported In: | 5.1.80 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
RJVB
2017-10-17 09:31:55 UTC
(Oops, DrKonqi manipulation error) It looks like the actual crash happened in ContextBrowserView::isLocked() but that the reason is the delivery of a pending event to a view after it was deleted but not (yet) unregistered. I'm not sure how that's even possible, but maybe the context browser should simply be disabled (and all views unregistered) in reaction to the `aboutToShutdown` signal? This output from the calling terminal may hint at what happened: virtual KDevelop::IAssistant::Ptr UnknownDeclarationProblem::solutionAssistant() const scanThread seems to have outlived its usefulness virtual KDevelop::IAssistant::Ptr UnknownDeclarationProblem::solutionAssistant() const scanThread seems to have outlived its usefulness KCrash: Application 'kdevelop' crashing... KCrash: Attempting to start /opt/local/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/505/kdeinit5__0 (I'd been applying an apt upgrade and the project took twice as long to load as it normally does, I may have run into a timing issue that caused the trigger event to be delivered just too late ... but that shouldn't cause crashing IMHO.) Thank you for the crash report. 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/worksforme" 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! |