Memory-related improvements (size_t, -Xmx1g, dynamic max heap)

#157 Open
Repository
Chewi
Branch
default
Repository
cacaovm
Branch
default

Bitbucket cannot automatically merge this request.

The commits that make up this pull request have been removed.

Bitbucket cannot automatically merge this request due to conflicts.

Review the conflicts on the Overview tab. You can then either decline the request or merge it manually on your local system using the following commands:

hg update default
hg pull -r default https://bitbucket.org/Chewi/cacao-staging
hg merge 85b4bd9eceec
hg commit -m 'Merged in Chewi/cacao-staging (pull request #157)'
Author
  1. James Le Cuirot
Reviewers
Description

These 3 commits aren't strictly dependent on each other but they are closely related. I must admit that I was surprised how bad the handling for this was. Perhaps this stuff was put together during the 32-bit era when heap requirements were much lower.

I've only tried this as part of an IcedTea build but it works well there. Note that -XshowSettings:vm will still show the requested -Xmx amount, even if an overflow caused that amount to be rejected. Runtime.getRuntime().maxMemory() subsequently returns the corrected amount.

Comments (0)