-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
graal_tear_down_isolate
stuck when Java2D Disposer
is running
#5339
Comments
graal_tear_down_isolate stuck
when Java2D Disposer
is runninggraal_tear_down_isolate
stuck when Java2D Disposer
is running
Hi, Thank you for reporting this issue, this is tracked internally on GR 42292. |
experiencing similar issue (win and macos) |
@oubidar-Abderrahim is there any update? |
1 similar comment
@oubidar-Abderrahim is there any update? |
The team is still investigating the issue. |
any update you may have would be greatly appreciated |
Hi @k-x7 we are currently working on #4921 to quite generally improve support for AWT and related technologies. Once that is merged (work is in progress already, so expect that to be merged in the next months, but no definite ETA), we will have a look at this. Could easily be affected by the current changes so we will have a look once the major changes are in. -- Christian |
any updates on this?? Facing similar issue while using a dependency that relies on awt. Even tried it with the latest graalvm dev builds, doesn't work. The issue described by @k-x7 is still reproducible with:
|
Describe the issue
I have created a small shared lib using native image, which call
ImageIO.read(...)
.when I call
graal_tear_down_isolate
from the C code the program will not return anything after printing an error :My assumption is Disposer when the thread interrupted it will just print the error and call
wait()
somewhere else, which will stuck in waiting state or the infinite while loop.I tried to get
Java2D Disposer
thread and callinterrupt()
many times without success.Steps to reproduce the issue
GetImageInfo.java
:javac
:output:
main.c
:main.c
:main
:now the program stuck forever.
ps
in the running program will show the following:Describe GraalVM and your environment:
Tested on release and last snapshot, Linux amd64:
The text was updated successfully, but these errors were encountered: