Bug 9290 - error MT2001: Could not link assemblies. Reason: Too many open files
Summary: error MT2001: Could not link assemblies. Reason: Too many open files
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 5.99.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2013-01-04 17:39 UTC by Marek Safar
Modified: 2015-04-16 11:11 UTC (History)
4 users (show)

Tags:
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:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Marek Safar 2013-01-04 17:39:24 UTC
When linking large project with many assemblies.

We are probably leaking some file references
Comment 1 Miguel de Icaza [MSFT] 2013-02-12 00:24:04 UTC
Can you point us to a sample that exhibits this problem?

It should be easy once we have the sample to run lsof to find out which file is being kept open for too long.
Comment 2 Marek Safar 2014-09-02 08:14:45 UTC
I don't have sample at hand but it can be quite easily generated. You generate .csproj file with hundreds of reference dlls (for example from mono/mcs/tests).
Comment 3 Sebastien Pouliot 2014-09-02 08:18:31 UTC
I never seen it, neither by myself or being reported. 
If it's easy to reproduce then please attach one and I'll have a look.
Comment 4 Sebastien Pouliot 2015-04-16 11:11:38 UTC
I have never hit that condition, even with very large customer projects. It might be because the underlying issue was fixed (e.g. inside mono) and I just never had a huge project at the time it was an existing issue.

Please re-open, with a test case, if that situation still happens.