Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
When linking large project with many assemblies.
We are probably leaking some file references
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.
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).
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.
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.