If we don't emit result, the ExecuteCompositeJob doesn't relise that
it's failing and keeps the dangling object. Calling stop all processes
would result in a crash then.
Details
Details
- Reviewers
mwolff - Group Reviewers
KDevelop - Commits
- R32:8430d3058f92: Make sure we don't crash when stopping all jobs
- run app
- run app again
- choose to kill the first instance
- stop all processes
Diff Detail
Diff Detail
- Repository
- R32 KDevelop
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
we got tons of reports for crashes in this regard, is this the reason? are there maybe more places that this needs to be fixed? one way or another, I think you can add at least one BUG: line
Comment Actions
we got tons of reports for crashes in this regard, is this the reason? are there maybe more places that this needs to be fixed? one way or another, I think you can add at least one BUG: line
Have been looking for a bug, couldn't find it.
I'll backport it to 5.2.
¯\_(ツ)_/¯