3

I'm using a List of QProcess objects to keep track of some processes that need to be start/stopped at user defined intervals.

I'm able to start and stop the processes OK. But the issue arises when I stop a process using the following methods (Pseudo code):

process->start("PathToProcess","Some Arguments");
//Do some stuff.
process->terminate();

However, if I try to start the process again at another time, I get the error:

QProcess::start:  Process is already running

I can do a ps -ef|grep processName and find that it is indeed dead, but it's sitting in a defunct state which I think is preventing me from starting it again.

What do I need to do to prevent this defunct state, or remove the defunct method so I can start my process again without reconstruction?

Chase Henslee
  • 3,918
  • 1
  • 18
  • 21
  • have you checked that `process->processState != NotRunning`? Sometimes the children die/crash without proper exiting. – mbx Aug 18 '11 at 20:15
  • After the terminate and after a kill I added for more testing, the process still shows as "Running" despite being in a defunct state in the OS. Good call. Seems like I may need to do setProcessState myself. – Chase Henslee Aug 18 '11 at 20:54

2 Answers2

8

Figured out what was causing the error.

In qprocess_unix.cpp, you'll find a class called QProcessManager. Essentially this class has signal handlers that watch for child processes that have died. When a child dies, the QProcessManager sends a message across a pipe that lets the QProcess class know that it terminated/died.

In a unrelated part of my code, I had set up some signal catching statements that I used for various puposes. However, these signal catches were catching my SIGCHLD event and thus the QProcessManager was never being triggered to pipe to the QProcess that it died.

In my case, my only options are to either watch for the death of the child manually or to remove the signal catching I'm performing in my other sections of code.

For future reference, if you have this problem, you may be better off doing POSIX calls for kills and terminates, and checking the return value of those calls manually. If success, perform a:

process->setProcessState(ProcessState::NotRunning);//Specify the process is no longer running
waitpid(process->pid(),NULL,WNOHANG); //Clear the defunct process.

Thanks all.

Chase Henslee
  • 3,918
  • 1
  • 18
  • 21
2

Call process->waitForFinished() after calling process->terminate() in order to reap the zombie process. Then you can reuse the process object.

Ken Bloom
  • 57,498
  • 14
  • 111
  • 168
  • Not looking good. When the process ends it's not emitting a finished() signal so the waitForFinished() never triggers. I assumed that when a program terminated, it would change the state from Running to NotRunning, but it doesn't look like that's the case. I'll keep looking at it. – Chase Henslee Aug 18 '11 at 20:46
  • When I tested with `process->start("sleep 60"); process->terminate(); process->waitForFinished();` it worked for me. – Ken Bloom Aug 18 '11 at 22:10
  • For some reason my "process->terminate()" never sends a finished() signal. So waitForFinished() is failing for me. – Chase Henslee Aug 19 '11 at 13:34