| Summary: | KDevelop crashes when terminating a running program | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Lucas Pires Camargo <lucaspcamargo> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bugs.kde.org, igorkuo, mail |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.4.6 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/kdevelop/kdevelop/commit/147add2ed8b3eac24b6bbd1af818f4685ab2aced | Version Fixed In: | 5.6.1 |
| Sentry Crash Report: | |||
| Attachments: |
Another stack trace
Happened again, crash in KJob::kill() |
||
|
Description
Lucas Pires Camargo
2020-01-28 17:17:00 UTC
Oh wait, I have edited the bug title accordingly. I now crashes every time when opening the session, and looking at the stack trace more closely, there seems to be something wrong with the editor component. What's that trace? The one you posted clearly points to the output view. Sorry, I had to carry on working and cleared the cache. After that, it stopped crashing. Oh, and you are right, sorry, I glanced at output view and though it had to do with Katepart for some reason. Created attachment 125495 [details]
Another stack trace
Ok, it keeps happening. KJob::kill() seems to be the culprit, not really the output view. As for the first stack trace, it looks as if KJob::kill() jumped to a random location in the output pane plugin, but not the second time. Uninitialized/corrupted function pointer maybe? ._.
Created attachment 125662 [details]
Happened again, crash in KJob::kill()
This may be a bug in Frameworks
I had this problem in every version change, also in the new version 5.5.0 It was solved by activating the "KDevGenericManager" add-on In other versions this add-on was deactivated when upgrading, in version 5.5 it was activated (apparently), so I deactivated it... I applied... I activated it again... applied... and the problem was solved. (In reply to Anon from comment #7) > I had this problem in every version change, also in the new version 5.5.0 It > was solved by activating the "KDevGenericManager" add-on > > In other versions this add-on was deactivated when upgrading, in version 5.5 > it was activated (apparently), so I deactivated it... I applied... I > activated it again... applied... and the problem was solved. I have tried that, to no avail. I got the work done anyways and when KDevelop crashed I'd just restart it. A bit annoying but not a dealbreaker for me. For my next project I'm moving to VS Code because of the embedded systems dev plugins. I'll spin up KDevelop again when the time comes. It's a great IDE for Cpp+Python projects, for sure. A possibly relevant merge request was started @ https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/167 This crash can be reproduced reliably with the following steps: 1. Execute-Launch an application from KDevelop. 2. Repeat the 1st step with the same application while the previous instance is still running. 3. In the "Job Already Running" dialog that appears after the 2nd step click the Cancel button. 4. Press the "Stop All" button. Git commit 147add2ed8b3eac24b6bbd1af818f4685ab2aced by Igor Kushnir. Committed on 22/09/2020 at 11:55. Pushed by igorkushnir into branch '5.6'. Don't crash after Cancel in Job Already Running dialog When a user Execute-Launches an application a second time while the previously launched instance of this application is still running, the "Job Already Running" dialog appears with 3 buttons. If a user clicks the Cancel button, a NativeAppJob kills itself Quietly. This NativeAppJob belongs to an ExecuteCompositeJob, which is not notified when a subjob is killed Quietly. So the ExecuteCompositeJob keeps waiting for it to finish. When this waiting ExecuteCompositeJob is killed (e.g. via "Stop All" button or on KDevelop exit), it attempts to kill the subjob it believes is still running, but which in fact is long since destroyed. This usually causes a segmentation fault. Aleix Pol fixed a similar crash when the "Kill All Instances" button in the "Job Already Running" dialog is clicked in 8430d3058f92725b4e6b7d85d8d68550ce12ee79. Related: bug 399511 FIXED-IN: 5.6.1 M +1 -1 plugins/execute/nativeappjob.cpp https://invent.kde.org/kdevelop/kdevelop/commit/147add2ed8b3eac24b6bbd1af818f4685ab2aced |