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.
For example, when using DevExpress and eXpressApp libraries, projects have lots of different assembly references that are very nested. And so if I try to run or build one of my projects it takes something about a minute to check whether project should be built or no. During this process memory consumption constantly jumps from 200-300 Mb up to 1.2-1.3 Gb and back.
I've done some debugging and found out that MD rereads assembly definition via Cecil every time it's required. Which in turn causes the whole binary to be loaded into memory. My thought was to cache this data for the current MD session. There's a rough patch in attachment that shows the idea. With caching projects starts and build almost immediately. But I'm not sure whether it's correct and/or respects any style guides adopted by MD.
Created attachment 2199 [details]
It seems that switching to IKVM reflection fixed this bug without the need of introducing some caching.