I haven't seen this one; the code in TableView in onChanged hasn't had
any updates 6 years.
I have my doubts this is a JavaFX problem as it seems the Compiler is
crashing here in a piece of native code. It's possible this problem is
only occuring on systems where the compiler decides it needs to compile
(or recompile) this method, so at a minimum you'd need to make use of
TableView in a way to hits that code path often enough to trigger
compilation.
Oracle provides some documentation on how to deal with what looks like a
compiler bug, please read here:
https://docs.oracle.com/en/java/javase/17/troubleshoot/troubleshoot-system-crashes.html
Further, I think you should report this problem with as much details as
possible on bugs.openjdk.java.net -- you can look for similar bugs to
see what kind of detail and settings would be helpful to debug this.
Other things you could try to solve it yourself:
- Run a different Java version
- Try switching to a different GC
- Use different VM options (are you using anything special?)
- Anything else that is not often used, non-standard or experimental,
try going to a more common setup
--John
On 18/03/2022 09:43, Daniel Peintner wrote:
Hello,
I take the liberty to ask on the email reflector if there are other people
with similar problems.
Since updating my application to JavaFX18 I get random fatal crashes.
Unfortunately it is not predictable but after some time the app crashes
with "EXCEPTION_ACCESS_VIOLATION".
The hs_error_pidX reports the following.
--------------- T H R E A D ---------------
Current thread (0x0000016be9c9b410): JavaThread "C2 CompilerThread0"
daemon [_thread_in_native, id=3068,
stack(0x000000393e800000,0x000000393e900000)]
Current CompileTask:
C2:10515286 18185 4 javafx.scene.control.TableView$5::onChanged
(1049 bytes)
Am I the only one seeing this?
I am not sure if this relates to changing JavaFX 17 to 18 or whether it
makes it just more likely.
It seems to be related to "javafx.scene.control.TableView$5::onChanged"
since all crashes show this line.
Having said that, I cannot provide a test-case since it happens all of a
sudden and sometimes after hours using the application.
I am open to any feedback or input on how to proceed best.
Thanks!
-- Daniel
