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.
I have a XAML based UI with AbsoluteLayout and use TranslateTo() animations in code-behind. One 1 second TranslateTo() animation results in 20000 AbsoluteLayoutFlags allocations (shown in XF profiler) and I am not creating any new UI elements or allocating these structures in code-behind. Nor do I ever change AbsoluteLayoutFlags for existing UI elements.
So it seems there is a performance related bug in XF.
Thank you for taking the time to submit the bug. We tried to reproduce the issue you reported but were unable given the description. If you could please attach a reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue we would very much appreciate it. We monitor recently touched NEEDS INFO bugs so we’ll notice you attached the reproduction we’ll take it from there.
Xamarin Forms Team
This happened with an older version of XF and the profiler, so if you cannot duplicate it maybe it's best to just close this issue. Next time I do profiling I will look for it and reopen this issue if it still happens.
Ok, please open if you find it still happens