[Mono-bugs] [Bug 80143][Min] New - CreateProcess fails after about 4000 process starts

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by ivo at ufo-net.nl.

http://bugzilla.ximian.com/show_bug.cgi?id=80143

--- shadow/80143	2006-12-04 08:27:13.000000000 -0500
+++ shadow/80143.tmp.22964	2006-12-04 08:27:13.000000000 -0500
@@ -0,0 +1,56 @@
+Bug#: 80143
+Product: Mono: Class Libraries
+Version: 1.2
+OS: GNU/Linux [Other]
+OS Details: Debian Sarge
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: Ivo at UFO-Net.nl               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: CreateProcess fails after about 4000 process starts
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+Process.Start fails after 4092 repeats (always 4092 repeats in my
+testcase!) with a warning:
+** (ConsoleApplication1.exe:11324): WARNING **: CreateProcess: error
+creating process handle
+However, Process.Start still returns TRUE, the StandardOutput reports to be
+at it's end, but does not give any errors when trying to read a line.
+
+Steps to reproduce the problem:
+1. Create a variable of type System.Diagnostics.Process
+2. Set StartInfo.FileName and .Arguments to for example echo,
+.CreateNoWindow to true, RedirectStandardOutput to true, UseShellExecute to
+false
+3. Create an infinite loop with an optional counter. Inside the loop, call
+Process.Start. Optionally show an error message if
+Process.StandardOutput.EndOfStream returns true. Kill the process if it has
+not Exited yet and wait some milliseconds.
+
+Actual Results:
+My testcase gives a warning (followed by an exception, because
+Process.StandardOutput.EndOfStream returns true) after it has created 4092
+processes.
+The testcase does this all quite fast, so it's easy to actually test
+something. The original application spawned iptables every 5 seconds to
+check its traffic counters.
+There were no problems with the RRDTool process (wich was kept running).
+
+Expected Results:
+No warning, or at least Process.Start returning false when it fails.
+
+How often does this happen? 
+After 4092 calls to Process.Start with my testcase on my system. After that
+it keeps giving errors.
+
+Additional Information:
+Tested using a SVN compile of about 4 days ago.