Peter Quiring
Peter Quiring
I think once Graal is built with later JDKs that support for AWT will be included. The newer JDKs will most likely avoid using class init threads that are not...
It would appear as though SubstrateVM doesn't support AWT. https://github.com/oracle/graal/blob/master/substratevm/src/com.oracle.svm.core/src/com/oracle/svm/core/jdk/JavaAWTSubstitutions.java#L37 It's taken 5+ years to get to here. Adding AWT could take many more years.
Probably the only thing needed is to create the JNI config. But what about threads started in ctors? I think that was another issue.
An alternative is to build a --shared library and then build your own loader with JNI libraries baked in. That's what I do now. The loader just has to registerNatives()
My loaders are here: https://github.com/pquiring/javaforce/tree/master/stubs And JNI libraries are here: https://github.com/pquiring/javaforce/tree/master/native
Tried a different distro and is working now. CentOS = not available Debian/Ubuntu = fails openSUSE Tumbleweed = fails openSUSE Leap = works Thanks,
After trying to get rid of shared_ptr and create a garbage collector the performance is still very bad.
Ok, this issue is finally resolved. Q# now offers manual memory management or the Boehm-Demers-Weiser garbage collector.
Performance is still an issue.
[zgc.zip](https://github.com/user-attachments/files/17233004/zgc.zip) Attaching some ZGC logs. One for Linux and another for Win64 for comparison.