-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on GraalVM at 1.9.0-RC
#4146
Comments
@sgammon could you please provide an instruction on how to run a reproducer? |
@fzhinkin Yes, I have a reproducer. Here is one that works with a very simple native image build. It includes Coroutines It seems like most of the stacktraces I can produce point to coroutines and/or atomicfu. I have much more detailed tracing in the following issues:
Reproducer: I may need to file a bug with Micronaut as well if it relates to their code, but so far I don't see any hint that it does. I'm using the Micronaut project generator because it gets really close to our dependencies anyway (ours is a Micronaut/Picocli command line application). There seem to be multiple exceptions or crashes, or maybe multiple bugs interplaying, so if I come up with other reproducers I will post them here and on the tracking ticket. As far as I can tell, though, most hints points to either coroutines or atomicfu; specifically, the exception depicted surfaces if optimizations are in |
@sgammon, thank you for sharing the reproducer! I managed to reproduce the crash locally on macos-aarch64 with Graal EE 21, 22, and 23. For me, the issue also gone after switching optimization level to As a side note, commands to run the reproducer are (taken from the Graal's GH issue):
|
For the record, the stack trace I ended up with is:
|
I tried to debug the issue a bit more, and some outcomes so far:
|
The crash is reproducible with Kotlin 1.9.24, Mosaic 0.12.0 and some older compose version: 972-w-1924.zip |
It is also reproducible with GraalEE 17. In all crash occurrences, it seems like we're hitting NPE:
At the crash time, memory referred by |
@sgammon have you succeeded filing an issue against GraalVM? From where we are at, it seems like it's rather a Graal issue than not |
@qwwdfsad Yes, there is an issue filed with GraalVM. I'll try to cross tag it. I would have thought the same thing but I just recently witnessed this bug surface with Proguard too. It seems this issue can surface through bytecode optimization as well as AOT |
@sgammon, oracle/graal#9046 was closed as the assigned engineer is missing a reproducer published on github. Could you please take a look @ oracle/graal#9046 (comment)? |
Describe the bug
When building a GraalVM native image against coroutines
1.9.0-RC
, things mostly work but the following crash occurs under some conditions, for us with use of Mosaic and the new Kotlin-built-in Compose compiler:Provide a Reproducer
See here for a partner issue with detailed tracing. A reproducer is available.
The text was updated successfully, but these errors were encountered: