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
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.
This could be used to determine why an assembly/image is still kept in memory if the programmer expected it to be unloaded.
After some investigation, this is fairly simple to do: We just instrument the places where MonoAssembly::ref_count and MonoImage::ref_count are modified (4 in total).
However, the new profiler API should be implemented before this.
To actually provide useful information, we would need to also provide a 'reason' parameter that says why a reference was added/removed. That would be a quite a bit more work. Since this idea was mostly a nice-to-have with no current use cases, the effort isn't really worth it. Closing.