Bug 16119 - Process.Start leaves stray "open" processes
Summary: Process.Start leaves stray "open" processes
Alias: None
Product: Runtime
Classification: Mono
Component: io-layer ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-11-11 17:21 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-12-16 17:13 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Mikayla Hutchinson [MSFT] 2013-11-11 17:21:33 UTC
When using Process.Start with ProcessStartInfo.UseShellExecute=true and an url as the item to open, the "open" process stays alive until the web browser is closed. This is because it uses "open -W". Right now I have 15 "open" processes running on my system because of this.


I'm not sure why the -W argument is necessary. There's no reason to have a handle to the "open" process.
Comment 1 Rodrigo Kumpera 2013-12-16 17:13:34 UTC