Closed
Bug 453311
Opened 17 years ago
Closed 16 years ago
nsIProcess.exitValue is always -1 for a Non-Blocking process
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
People
(Reporter: nithinkumary2k, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0
nsIProcess spawns non block processes in a 'fire and forget' fashion. There doesn't seem to be a way of finding anything about it after it's spawned.
nSIProcess.run() should return the pid of the process. But it returns 0 when the blocking flag is set to false. (try to run process in Non-Blocking mode)
nsIProcess.exitValue always returns -1 for a Non-Blocking process even though the process is running.
Reproducible: Always
Steps to Reproduce:
1. invoke the nsIProces.run with the blocking flag set to false
2. alert the return value.
3. Check the nsIProcess.exitValue periodically.
Actual Results:
nsIProcess.run() returns zero and and nsIProcess.exitValue always returns -1
Expected Results:
nsIProcess.run() should return the pid of the process and it should set the nsIProcess.exitvalue to -1 only after its terimination.
Updated•17 years ago
|
Version: unspecified → Trunk
Comment 1•16 years ago
|
||
This was fixed by bug 480427
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•