Open aalmiray opened 2 years ago
Hello @aalmiray, I will take a look at this issue. If I have any questions I will let you know.
This issue has surfaced again https://github.com/jreleaser/jreleaser/actions/runs/4546403129/jobs/8017802452
I believe this commit is the one that causes the build to break https://github.com/jreleaser/jreleaser/commit/0a5c4baa51414d1b7b391a341ac270380e713c64 It has nothing to do with GraalVM Native Image settings. Rather I think it's the code size. Linux and MacOS are working as expected, only Windows fails.
As mentioned in https://github.com/oracle/graal/issues/3171#issuecomment-860643090, this appears to be an OutOfmemory error within the VS linker. This also explains why you got the error without touching anything GraalVM-related. The Windows runners have limited memory (7GB) and if GitHub decides to update the VS installation in their runner, a newer version of the VS linker may require more memory. If that is just too much for the 7GB, the linker will fail. We are hitting this issue ourselves in some places and are looking for a way to mitigate this problem.
Describe the issue Stumbled upon this issue when building a native image using https://github.com/marketplace/actions/github-action-for-graalvm on
windows-latest
Steps to reproduce the issue Please include both build steps as well as run steps
https://github.com/aalmiray/test
Describe GraalVM and your environment:
More details
Command line used to build the image
Build job defined as https://github.com/aalmiray/test/blob/cc26b57df7413d7c3b8201c10a68e681d3e324b7/.github/workflows/native-image.yml#L6-L78
Failed workflow run available at https://github.com/aalmiray/test/actions/runs/1674682341