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.
The frequent GC (every 1 second) on the simulator makes it quite hard for very long profiling sessions.
The problem is that each GC, even when not producing a heap dump, it collects quite some data.
It would be nice to get this fixed for C7.
Even better if the fix lands in a C6 service release.
Already discussed by mail, so adding it here for reference: apart from disabling it in x.ios, would the IDEs need to pass --nodebugtrack to mtouch when building/deploying?
--nodebugtrack is a temporary workaround until this has been implemented.
Rolf, what would be the implementation be?
To do --nodebugtrack implicitly when some other flag is enabled? If so which?
@Miguel, the implementation would stop the GC.Collect loop when a profiler is attached (this is done at runtime, so that the app doesn't have to be rebuilt).
*** Bug 38144 has been marked as a duplicate of this bug. ***