https://bugzilla.novell.com/show_bug.cgi?id=679936
https://bugzilla.novell.com/show_bug.cgi?id=679936#c0 Summary: Process.Start leaves child processes around unless WaitForExit() is called Classification: Mono Product: Mono: Runtime Version: 2.10.x Platform: x86 OS/Version: Mac OS X 10.6 Status: NEW Severity: Normal Priority: P5 - None Component: io-layer AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Found By: --- Blocker: --- Created an attachment (id=419528) --> (http://bugzilla.novell.com/attachment.cgi?id=419528) ProcessTest.cs file User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 Running the attached program will eventually crash on Mac because the limit for kern.maxprocperuid will be reached. The problem appears to be that Process.Dispose() doesn't cleanup everything that it should and processes are still hanging around. Reproducible: Always Steps to Reproduce: 1. Compile the attached program. 2. Open two Terminals 3. Run the attached program in one terminal and in the other terminal, run "ps -x" while the program is running. You should see lots of "echo" processes hanging around. Actual Results: Eventually the call to fork() will fail and you'll get a Win32Exception. Expected Results: Process.Dispose() should not leave the processes hanging around. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
