1. 22 Sep, 2020 1 commit
    • Igor Kushnir's avatar
      Don't crash after Cancel in Job Already Running dialog · 147add2e
      Igor Kushnir authored
      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
      8430d305.
      
      BUG: 399511, 416874
      FIXED-IN: 5.6.1
      147add2e
  2. 10 Sep, 2020 2 commits
  3. 07 Sep, 2020 3 commits
  4. 05 Sep, 2020 1 commit
  5. 03 Sep, 2020 1 commit
  6. 02 Sep, 2020 1 commit
    • Igor Kushnir's avatar
      Remove a duplicate qCWarning(SHELL) · 817be892
      Igor Kushnir authored
      355124b2 (master branch) upper-cased the
      first letter of this warning. bda72ef1
      (branch 5.1) switched from qWarning() to qCWarning(SHELL).
      33f15abf merged 5.1 into master, but
      ended up including two almost identical warnings. This commit removes
      the warning that starts with a lower-case letter.
      817be892
  7. 31 Aug, 2020 1 commit
  8. 28 Aug, 2020 1 commit
  9. 27 Aug, 2020 1 commit
  10. 26 Aug, 2020 1 commit
  11. 23 Aug, 2020 1 commit
  12. 22 Aug, 2020 1 commit
  13. 17 Aug, 2020 3 commits
  14. 16 Aug, 2020 4 commits
  15. 14 Aug, 2020 10 commits
  16. 12 Aug, 2020 3 commits
  17. 06 Aug, 2020 5 commits