Bug 10172 - Xamarin: Low available memory on the heap (HelloWorld)
Summary: Xamarin: Low available memory on the heap (HelloWorld)
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.6.x
Hardware: Other Other
: Low normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-02-08 12:02 UTC by Marcelo Macedo de Melo Silva
Modified: 2017-07-06 18:23 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Android Heap (245.44 KB, image/jpeg)
2013-02-08 12:02 UTC, Marcelo Macedo de Melo Silva

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 Marcelo Macedo de Melo Silva 2013-02-08 12:02:44 UTC
Created attachment 3349 [details]
Android Heap


I create a Hello World APP (a blank project), and the Heap have 94,43% (See the atachted image).

Don't have files, database, nothing.. but the 1-Byte Array no Heap have 6,576MB.

Can you helpe-me to understand this?


Comment 1 Cody Beyer (MSFT) 2017-07-06 18:23:56 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.