Open holly-cummins opened 7 months ago
Similar stack trace to https://github.com/quarkusio/quarkus/issues/32209, but that’s old, and fixed.
The tests are limited to running with 128m in RunAndCheckMojoBase
.
It looks like this is a straw-that-broke-the-camels-back scenario, because with 3.6 I can get an OOM in the test by shrinking my heap to 110M.
I can reproduce, even with Quarkus 3.6, by running the app with mvn quarkus:dev -Djvm.args='-Xmx110m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Users/holly'
Steps to reproduce
cd quarkus-pact/cross-extension-integration-tests/target/test-classes/projects/happy-everyone-all-together-processed
mvn quarkus:dev -Djvm.args=“-Xmx110m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=~”
Here's the MAT Top Consumers view for 3.7:
I've worked around this in the short term by increasing the heap given to the tests in https://github.com/quarkiverse/quarkus-pact/pull/177.
I've raised https://github.com/quarkusio/quarkus/issues/38814 to track the issue on the Quarkus side.
This is causing the current failures on https://github.com/quarkiverse/quarkiverse/issues/94, and it's also blocking any update to Quarkus 3.7.
The failure can be avoided by disabling the
DevModeContractTestIT
in the cross-extension project.