Details
-
Bug
-
Resolution: Out of scope
-
P4: Low
-
4.4.1
-
None
Description
Test case: connect error signal to a slot that, in case the error is QProcess::crashed, deletes the QProcess, and then continue normally.
Expected: QProcess (representing the already-crashed and known-to-be-crashed) process to quickly delete and continue with normal program execution. Instead: It just freezes, blocking indefinitely in waitForFinished.
This happens no matter when the crash takes place - including after some communication between the two processes had already taken place, so it seems as if it couldn't be a race condition.
Note: deleting the sender object from inside a slot is never a good practice. This task has a low priority because of that.