Have a overloaded method for process.start so it does not inherit handles - by Noktruene

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 771517 Comments
Status Resolved Workarounds
Type Bug Repros 0
Opened 11/17/2012 6:33:34 PM
Access Restriction Public


Would it be possible in the next version of .net to include an overloaded method of process.start so it DOES NOT inherit the handles of the starting process? We have a network application that is starting a child process and when it crashes the ports are not closed as the child process is still running (most cases we have to reboot the box to get the application working again). 

1. Process A starts.
2. Process A opens a TCP port.
3. Process A starts Process B using System.Diagnostics.Process.Start
4. Process A terminates unexpectedly, and does not properly close its TCP port.
5. Process B maintains a copy of the handle to the TCP port.
6. As there is an existing open handle, the Operating System does not close the port when cleaning up dead resources for process A.

This URL goes it better detail 


Sign in to post a comment.
Posted by Microsoft on 2/21/2013 at 7:23 AM
Thank you for your feedback. We are not going to be able to address this issue in our next release due to other priorities.

Immo Landwerth
.NET Framework team
Posted by Microsoft on 11/19/2012 at 9:56 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Microsoft Visual Studio Connect Support Team for triage and resolution. These specialized experts will follow-up with your issue
Posted by Microsoft on 11/19/2012 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)