Bug 3732 - Out of memory error when extracting resources from large assemblies
Summary: Out of memory error when extracting resources from large assemblies
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: PC Mac OS
: Low normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-03-02 15:57 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-04-02 15:56 UTC (History)
2 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 Developer Community or GitHub 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] 2012-03-02 15:57:27 UTC
User have reported that they occasionally encounter "out of memory" errors in MonoDevelop when it's extracting resources from a large dll (~130MB).

This doesn't seem likely to be a MD issue directly, since MD is using the Cecil stream API:
embeddedResource.GetResourceStream ().CopyTo (fileStream);

I dug into Cecil a bit, and as far as I can tell it actually loads the entire assembly into memory, instead of mmaping or loading from the FileStream as needed. I filed an issue upstream: https://github.com/jbevain/cecil/issues/94

Since the problem happens infrequently, my guess is that there is a leak somewhere in MD, and the loading of the assembly is the final straw.
Comment 2 Jeffrey Stedfast 2013-04-02 15:56:06 UTC
this has been fixed