-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Building an image with conscrypt included throws an VMError (Image heap writing found a class not seen during static analysis) #6793
Comments
Two objects of the class The two The archive
And the archive also contains the two X.509 certificates, loaded into the two |
@loicottet, I believe the changes relative to this new behavior were introduced in this commit. Do you think this new behavior introduced a regression? |
This commit introduced reflective access to signers in Native Image, so it is possible that the issue comes from here. What looks strange to me is that there are no signers registered in the |
I have the same issue with Bouncy Castle when using |
@loicottet, did you make any progress on this? It seems other place on the internet have the same issue (quick google search). I tried it with the latest / greatest Oracle GraalVM and the issue still persists. Just FYI, if I were to remove the META-INF/MANIFEST.MF
META-INF/MANIFEST.MF
and remove repackage with
|
Not sure if my issue is related. I want to use the
Of course I tried looking around files that could have this dependency, but no dice. I tried both 21.0.1 and 17.0.9 but no luck. |
This is caused by the fact that signers are mistakenly included in the image even if they are not registered as reflectively accessible, as well as the fact that signer classes are not correctly registered during analysis when they are. I have a fix on the way for these issues. |
would it be possible to backport it to 23.x? |
Yes, we can do that |
Describe the issue
Trying to build a native-image with conscrypt (https://github.com/google/conscrypt) included.
Steps to reproduce the issue
README.md
instructions in RepoDescribe GraalVM and your environment:
More details
Using following settings (see repository example) will result in an Error when generating an native-image with GraalVM CE native-image 23.0. With GraalVM CE 22.3.x the generation of the native-image succeeds without any issue.
Is there any guidance what I should do in such cases?
The text was updated successfully, but these errors were encountered: