Johan Vos
2018-11-27 17:53:32 UTC
An easy to reproduce issue is to change permissions on the cache dir used
by Javafx for storing native libs.
If JavaFX can't write anymore to that cache dir, applications will fail
since all pipelines use native code.
The fix at https://github.com/javafxports/openjdk-jfx/pull/300 makes the
caching mechanism more robust, with a fallback to the tmp dir, and with the
option to always override the location of the cache dir.
Note: In the end, I still hope this is something that can be provide by the
JDK itself (extracting native code from jars or jmods and storing it). For
now, we probably just want to make the system more robust.
- Johan
by Javafx for storing native libs.
If JavaFX can't write anymore to that cache dir, applications will fail
since all pipelines use native code.
The fix at https://github.com/javafxports/openjdk-jfx/pull/300 makes the
caching mechanism more robust, with a fallback to the tmp dir, and with the
option to always override the location of the cache dir.
Note: In the end, I still hope this is something that can be provide by the
JDK itself (extracting native code from jars or jmods and storing it). For
now, we probably just want to make the system more robust.
- Johan