bootcycle build on ix86-linux-gnu broken since jdk-13+18

Matthias Klose doko at
Wed Jun 19 20:44:05 UTC 2019

On 19.06.19 19:06, Ioi Lam wrote:
> On 6/19/19 5:12 AM, Andrew Haley wrote:
>> On 6/14/19 1:57 PM, Matthias Klose wrote:
>>> Compiling 12 properties into resource bundles for jdk.jdeps
>>> #
>>> # There is insufficient memory for the Java Runtime Environment to continue.
>>> # Native memory allocation (malloc) failed to allocate 2155274940 bytes for
>>> AllocateHeap
>>> # An error report file with more information is saved as:
>>> It looks like the normal build instead of the bootcycle build succeeds.  Does
>>> anybody else is doing regular ix86 builds and could help narrowing down when
>>> this started to fail?
>> Is this a 32-bit x86 kernel virtual machione or are you building a
>> 32-bit JDK in a 64-bit environment? What does cat /proc/meminfo say?

this is a pure 32bit chroot, run with a 64bit kernel, using the linux32
personality to enter the chroot.  The build should not see any hint about the
64bit kernel.

The bootstrap JDK is OpenJDK 12 (32bit).  Most buildd infrastructure for any
Linux distribution doesn't mix 32/64 bit, including Fedora, Debian, Ubuntu.

> Andrew, the bug that causes the broken build is
> The failure doesn't always happen, but it's more likely to happen when your
> BOOT_JDK is significantly different than the JDK sources in both age and 32/64
> bit-ness.

yes, using the work-around, the build succeeds.

Thanks, Matthias

More information about the jdk-dev mailing list