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.
MonoDevelop is leaking heavily during normal usage, even with stetic disabled.
Is this still the case? I've never been able to reproduce a noticeable leak. We may as well close this if we can't get more info.
Yes. Every time I open and close Main.sln, MD's memory use grows another 30-100 MB, and it never goes back down.
Does this only happen on MacOS or does it happen on windows too?
I opened and closed main.sln several dozen times and saw a pretty negligible change in memory usage as compared to opening it just once. There's definitely a leak but it is miniscule, in the order of a few MB per open/close cycle you average out the memory increase.
If you can still repro 30-100 mb per open/close cycle with the latest builds we should look into it.
MacOS, tip of ui-refresh, bockbuild.
*** Bug 7611 has been marked as a duplicate of this bug. ***
Michael, is this fixed?
Can trivially repro on Windows. Simply keep opening and closing Main.sln.
The same bug still exists after your fix. The repro is even simpler. You can trigger it this way on Mac:
1) Delete ~/Library/Caches/XamarinStudio-4.0
2) Open XS
3) Open Main.sln (from the monodevelop repo) and the close it immediately
Memory usage increases forever and the CPU is consistently around 150%.
It is not the same bug. That is completely different.
(btw. that one should be fixed as well)