Bug 28406 - Garbage collection difference from .NET
Summary: Garbage collection difference from .NET
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: 3.12.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-03-25 09:15 UTC by John Miller [MSFT]
Modified: 2015-04-02 11:24 UTC (History)
4 users (show)

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


Attachments
Test Case (8.26 KB, application/zip)
2015-03-25 09:15 UTC, John Miller [MSFT]
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 FIXED

Description John Miller [MSFT] 2015-03-25 09:15:54 UTC
Created attachment 10495 [details]
Test Case

**Overview:**

   The attached project shows a difference in memory usage when run on Mac vs Windows. 
   On Windows, the memory usage does not climb. On Mac, it does. 

**Steps to Reproduce:**

   1. Run the attached sample on Mac OSX
   2. Once you see the line "Press any key to start iterating", press a key
   3. Wait
   4. Observe the memory usage of the application using Activity Monitor

**Actual Results:**

   Memory usage will continue to climb as the application "iterates".

**Expected Results:**

   Memory usage should not continue to climb. Expecting the same results as when it's run on Windows. 

**Build Date & Platform:**

   Mono 3.12.1

**Additional Information:**

   Run on Windows using .NET and the memory usage does not continue to climb.
Comment 1 Alexander Kyte 2015-03-30 14:52:14 UTC
I can confirm that this leaks memory at a pretty rapid rate on linux using mono 3.12, but using the master branch on commit 88f920a7e8e68e3b5f680a0e79be4dbc2e0890f4(currently head) shows no leak. I would suggest using mono from git until these fixes have been released.
Comment 2 Rodrigo Kumpera 2015-04-02 11:24:16 UTC
I can reproduce with mono 4.0 but not with master mono that features microsoft's System.Data.

The fix for this will ship on cycle 6.