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.
Mono 4.2 under FullAOT (as with iOS) has now the ability to use the managed allocator.
The managed allocator doesn't handle profiling which means we can't do alloc profiling when it's been used.
For debug build profiling, we can disable it, for release builds it will require something else.
Vlad / Zoltan, is my understanding of 4.2 correct?
What should we do to address this?
We could have all the calls that go to the managed allocator through the plt and also have another allocator that just jit icalls to mono_object_new_specific. At runtime when we decode MONO_WRAPPER_ALLOC, we just select the new allocator if the alloc profiling is enabled.
Why do we want to support allocation profiling in release mode ?
The profiler team wants to support profiling release builds.
Another solution is to rebuild the app for profiling which would disable the managed allocator.
This is supported since this commit: https://github.com/mono/mono/commit/398b9e66b0cb10c55c02d77aec80148c73979bde