Bug 20093 - Java Max Heap Size guidance is wrong
Summary: Java Max Heap Size guidance is wrong
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Dominique Louis
Depends on:
Reported: 2014-05-28 09:08 UTC by Rainer Mager
Modified: 2016-11-19 02:56 UTC (History)
6 users (show)

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 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 Rainer Mager 2014-05-28 09:08:30 UTC
In Visual Studio under the "Application" tab of a project's options there is the "Java Max Heap Size" field to adjust this setting. Under the field it says: "example: 100m or 1GB". The second example is incorrect, it should be "1G", without the "B".
Comment 1 Mohit Kheterpal 2014-05-28 09:28:57 UTC
This issue was already fixed as shown in screencast : http://screencast.com/t/kK7T0wDkCw7O

You will get fixed build sooner.
Comment 2 James Montemagno [MSFT] 2016-11-19 02:35:25 UTC
This is actually been updated again and is now Wrong Again. I am opening it up.

It says: example: 100 MB or 1 GB, which is wrong. Can we just explain it better in the IDE please.
Comment 3 Brendan Zagaeski (Xamarin Team, assistant) 2016-11-19 02:56:18 UTC
## Cross-referencing

A bug about the new incorrect text as discussed in Comment 2 has now been filed as Bug 47445.