Re: Seeking help with Java compile heap memory out-of-memory error on armel for zeroc-ice build
Hi,
Unfortunately I do not have an armel box accessible, but maybe
tweaking Gradle heap size through 'export GRADLE_OPTS=-Xmx<heapsize>'
might help?
I have tried with export GRADLE_OPTS=-Xmx512M and the package was
built successfully.
Best Regards,
Vladimir.
On Wed, May 1, 2024 at 4:08 PM Chris Knadle <Chris.Knadle@coredump.us> wrote:
>
> Greetings.
>
> I'm looking for some help for a build failure on armel related to
> compiling Java that has cropped up in the last couple of weeks. This is
> keeping Debian packages zeroc-ice as well as mumble from transitioning
> to Testing.
>
> The compile seems to fail during a Gradle / Java memory check and seems
> to be specific to armel.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069538
>
> I've done additional test builds on 2 armel Debian porter boxes and the
> error is repeatable.
>
> > :test:compileJava
> > Putting task artifact state for task ':test:compileJava' into context
> > took 0.0 secs.
> > Up-to-date check for task ':test:compileJava' took 47.549 secs. It is
> > not up-to-date because:
> > No history is available.
> > All input files are considered out-of-date for incremental task
> > ':test:compileJava'.
> > Use of target 1.7 is no longer supported, switching to 8
> > Use of source 1.7 is no longer supported, switching to 8
> > Compiling with JDK Java compiler API.
> > Failed to execute
> > org.gradle.process.internal.health.memory.DefaultMemoryManager$MemoryCheck@12c1b75.
> > An exception has occurred in the compiler (17.0.11). Please file a bug
> > against the Java compiler via the Java bug reporting page
> > (https://bugreport.java.com) after checking the Bug Database
> > (https://bugs.java.com) for duplicates. Include your program, the
> > following diagnostic, and the parameters passed to the Java compiler
> > in your report. Thank you.
> > java.lang.OutOfMemoryError: Java heap space
> > :test:compileJava FAILED
> > :test:compileJava (Thread[Task worker for ':',5,main]) completed. Took
> > 48 mins 58.651 secs.
>
> I'd like to know how to fix or work around this bug if possible.
>
> Thanks
>
> --
>
> Chris Knadle
> Chris.Knadle@coredump.us
>
Reply to: