-
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
[native-image] SegFault Using Helidon, Google Cloud Libraries #3351
Comments
FYI I've just tried this with 21.1.0 (linux_amd64) Java 11 based and it's still an issue.
|
I've narrowed it down to something in |
I could not reproduce the issue due to some issues with Docker on my machine, is it possible to get a simpler reproducer? Does it cause an issue if used outside docker? |
I cannot find the |
Hi, Any updates on the reproducer? |
Unfortunately, I don't have a simple example. However, if you use my project dansiviter/helidon-gcp and build the native image:
Then run it: docker run --rm -it `
-p 8080:8080 `
-e CLOUDSDK_CONFIG=/gcloud `
-v $Env:APPDATA/gcloud/:/gcloud:ro `
helidon:native
Then fire off a few http://localhost:8080/v1/greet and it will crash. |
If this issue is still relevant in the latest GraalVM versions, please open a new issue and follow the template. Thank you |
Describe the issue
SegFault issue with application. Lack of understanding of how Graal static works has forced raising this ticket so hoping for either guidance or confirmation of it being a bug. The example app is Helidon integrated with Google Cloud Logging, Metrics & Tracing.
Steps to reproduce the issue
For Windows, run the following:
git clone --depth 1 --branch GraalSegFault https://github.com/dansiviter/helidon-gcp
docker build -f .\Dockerfile.native --no-cache -t helidon:native .
gcloud auth application-default login
docker run --rm -it -p 8080:8080 -e CLOUDSDK_CONFIG=/gcloud -v $Env:APPDATA/gcloud/:/gcloud:ro helidon:native
http://localhost:8080/v1/greet
Describe GraalVM and your environment:
More details
The text was updated successfully, but these errors were encountered: