andreenk
23rd March 2013, 19:23
Hi,
I watch the following strange behavior:
1) I have a global QProcess object. ( QProcess SomeProcess; )
2) I start a child process with this object, and it does not launch correctly due to the known bug in the child app.
3) Parent program continues
4) Later, when parent program finishes, it completely deadlocks with 100% CPU utilization inside that QProcess::~QProcess()
Is this a QT bug or I am doing something wrong?
QT 4.8.4 on Mac OS X 10.8
I watch the following strange behavior:
1) I have a global QProcess object. ( QProcess SomeProcess; )
2) I start a child process with this object, and it does not launch correctly due to the known bug in the child app.
3) Parent program continues
4) Later, when parent program finishes, it completely deadlocks with 100% CPU utilization inside that QProcess::~QProcess()
Is this a QT bug or I am doing something wrong?
QT 4.8.4 on Mac OS X 10.8