Bug 6437 - Memory leak in System.Diagnostics.Process
Summary: Memory leak in System.Diagnostics.Process
Status: RESOLVED DUPLICATE of bug 1682
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Martin Baulig
URL:
Depends on:
Blocks:
 
Reported: 2012-08-07 06:54 UTC by Stephan Hauser
Modified: 2013-01-11 16:23 UTC (History)
4 users (show)

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


Attachments
Test case showing the memory leak (384 bytes, text/plain)
2012-08-07 06:54 UTC, Stephan Hauser
Details


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:
Status:
RESOLVED DUPLICATE of bug 1682

Description Stephan Hauser 2012-08-07 06:54:22 UTC
Created attachment 2313 [details]
Test case showing the memory leak

Getting process information using the System.Diagnostics.Process API does not correctly release all resources when calling Process.Close().

Running mono-2.10.8.1 on Ubuntu 12.04.

The attached test case shows increased memory usage over time without ever releasing it. The mono objects themselves are freed, as shown by the log profiler.
Comment 2 Rodrigo Kumpera 2013-01-11 16:23:12 UTC
Yes, it's fixed.

*** This bug has been marked as a duplicate of bug 1682 ***