https://bugs.kde.org/show_bug.cgi?id=399511
Igor Kushnir <igor...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Version Fixed In| |5.6.1
Latest Commit| |https://invent.kde.org/kdev
| |elop/kdevelop/commit/147add
| |2ed8b3eac24b6bbd1af818f4685
| |ab2aced
Resolution|--- |FIXED
--- Comment #3 from Igor Kushnir <igor...@gmail.com> ---
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 416874
FIXED-IN: 5.6.1
M +1 -1 plugins/execute/nativeappjob.cpp
https://invent.kde.org/kdevelop/kdevelop/commit/147add2ed8b3eac24b6bbd1af818f4685ab2aced
--
You are receiving this mail because:
You are watching all bug changes.
