Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Vladimir Petko Newsgroups: linux.debian.maint.java Subject: Re: Seeking help with Java compile heap memory out-of-memory error on armel for zeroc-ice build Date: Thu, 02 May 2024 04:00:01 +0200 Message-ID: References: X-Original-To: Chris Knadle X-Mailbox-Line: From debian-java-request@lists.debian.org Thu May 2 01:55:34 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.855 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-2.355, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: AOJu0YwnUSGQi7IjCaXzKnAwBzyLfNVGT1xeaKhS1OVsDFOKKFK9nilo fKtbMqi46/7rJ7sb6V3kxepmoEW+CXo/zUWCZGZcDQUAQZbyuXlmlOqkHBHs7FwZb9gbe4P8RpW pLkUdBVwaCAlhG8z0pPMe2xBA7Y9DqafQxN9kd3Z+VBhB6wrRDQUfQyXkytB3UQoGML/yrzNLn/ cYRHe1JVY5wz6UznxIm1AS7jEFr1Lpy3d82d5qQVJqSI4vcZuuo0lGhA8J7blrQlQ= X-Received: by 2002:a0d:d412:0:b0:61b:eabc:76b5 with SMTP id w18-20020a0dd412000000b0061beabc76b5mr3788490ywd.2.1714614903136; Wed, 01 May 2024 18:55:03 -0700 (PDT) X-Google-SMTP-Source: AGHT+IE7Vk2niYhy086veeR5fEZO3zNgvPDMZp9Vln03m6EapZYoviiF+BM34v2HXDGVP3KDAD57l63AIrVwcIQ5hNg= X-Received: by 2002:a0d:d412:0:b0:61b:eabc:76b5 with SMTP id w18-20020a0dd412000000b0061beabc76b5mr3788485ywd.2.1714614902833; Wed, 01 May 2024 18:55:02 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/23445 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CALFf3kcrM4zsGUiAwJQrEf2Fqo5vuanLGSdaoZrHx8tO0PjGGg@mail.gmail.com Approved: robomod@news.nic.it Lines: 63 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-java@lists.debian.org X-Original-Date: Thu, 2 May 2024 13:54:51 +1200 X-Original-Message-ID: X-Original-References: <346d631a-da49-4684-af7e-c04694e4d5bc@coredump.us> Xref: csiph.com linux.debian.maint.java:12756 Hi, Unfortunately I do not have an armel box accessible, but maybe tweaking Gradle heap size through 'export GRADLE_OPTS=3D-Xmx' might help? I have tried with export GRADLE_OPTS=3D-Xmx512M and the package was built successfully. Best Regards, Vladimir. On Wed, May 1, 2024 at 4:08=E2=80=AFPM Chris Knadle 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=3D1069538 > > 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$MemoryCh= eck@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 >