Bug 52415 - Frame renderers uses a lot of memory.
Summary: Frame renderers uses a lot of memory.
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.3.3
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Chris King
Depends on:
Reported: 2017-02-09 10:25 UTC by Luigi Maestrelli
Modified: 2017-06-19 21:18 UTC (History)
4 users (show)

Tags: bug, android, memory, custom renderer, frame, ac
Is this bug a regression?: ---
Last known good build:

Project to reproduce (191.98 KB, application/x-rar)
2017-02-09 10:25 UTC, Luigi Maestrelli

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 for Bug 52415 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Luigi Maestrelli 2017-02-09 10:25:03 UTC
Created attachment 19770 [details]
Project to reproduce

The simple action to add an empty frame renderer causes the app to uses up to 10MB in memory. Without the renderer, it uses about 5MB.

In my real project, the renderer is adding up to 13MB in the app's memory usage.

This values was captured using the reproduction app attached and the Android DDMS.

To reproduce the issue measure the app's memory with and without the ExportRenderer attribute.
Comment 1 Jimmy [MSFT] 2017-03-08 23:29:48 UTC
Thank you for filing this report! I ran the attached project on a BLU R1 HD Android 6.0 device and got the following results using DDMS:

## With Renderer 
- Allocated:    9.7MB
- Heap:         13.7MB

## Without Renderer
- Allocated:    7.5MB
- Heap:         11.5MB

There is a memory increase when simply just registering a custom renderer even if the renderer doesn't do anything so I am confirming this report so the team can investigate further.