Bug 26357 - Xamarin profiler shows huge number of Xamarin.Forms.AbsoluteLayoutFlags allocations
Summary: Xamarin profiler shows huge number of Xamarin.Forms.AbsoluteLayoutFlags alloc...
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-01-23 14:26 UTC by philip
Modified: 2015-05-29 14:10 UTC (History)
5 users (show)

Tags: all absolutelayout performance
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description philip 2015-01-23 14:26:20 UTC
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.
Comment 1 Rui Marinho 2015-05-29 10:50:19 UTC
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. 

Warm regards,
Xamarin Forms Team
Comment 2 philip 2015-05-29 13:28:50 UTC

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.

Comment 3 Rui Marinho 2015-05-29 14:10:41 UTC
Ok, please open if you find it still happens