Don't apply pointer multipler to heap sizes on Android.

Don't apply pointer multipler to heap sizes on Android.

Android doesn't have swap space so if the heap goes over the physical memory
size the system will just kill us. Applying the Heap::kPointerMultipler
to heap size could cause the max heap size to be larger than physical memory.
Instead use the defaults which are based on actual physical memory configured
by Api::ConfigureDefaults().

BUG=432909
LOG=N

Committed: https://crrev.com/7611aace3e7bf6a3a25deb899ff2dc3bab1a8e66
Cr-Commit-Position: refs/heads/master@{#26954}

[rmcilroy, 2015-03-02 21:50:28]

rmcilroy@chromium.org changed reviewers:
+ hpayer@chromium.org

[rmcilroy, 2015-03-02 21:50:28]

Hannes: PTAL, thanks.  This is to fix crbug.com/432909

[Hannes Payer (out of office), 2015-03-02 22:04:27]

LGTM, this change will tank 64-bit android devices.

[rmcilroy, 2015-03-03 10:14:45]

On 2015/03/02 22:04:27, Hannes Payer wrote:
> LGTM, this change will tank 64-bit android devices.

Thanks.  One thing we could do if this does tank 64-bit android too much is use
the pointer multiplier to increase the semi-space size, but not the old-space. 
Would this help do you think?

[rmcilroy, 2015-03-03 10:14:48]

The CQ bit was checked by rmcilroy@chromium.org

[commit-bot: I haz the power, 2015-03-03 10:16:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/960213007/20001

[commit-bot: I haz the power, 2015-03-03 10:19:03]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-03-03 10:19:13]

Patchset 2 (id:??) landed as
https://crrev.com/7611aace3e7bf6a3a25deb899ff2dc3bab1a8e66
Cr-Commit-Position: refs/heads/master@{#26954}