All,
Thank you very much for all the comments/suggestions.
I have been learning a lot about JVM C2 compilation the last couple of days.
BTW, in the meanwhile a similar bug has been reported with Debian Linux and
has been added to https://bugs.openjdk.java.net/browse/JDK-828338
I wonder, could you do the opposite and force compilation to trigger the bug
more consistently?
Scott
> On Mar 18, 2022, at 2:03 PM, Philip Race wrote:
>
> I have at least seen JIT compiler crashes like this in other unrelated
> cases ..
>
> in theory you can use an option like
>
>
I have at least seen JIT compiler crashes like this in other unrelated
cases ..
in theory you can use an option like
-XX:CompileCommand=exclude,javafx/scene/control/TableView$5::onChanged
although I am very unsure about the syntax for the last part of it
especially with what looks like
some
Thanks, Phil. That was my take as well. I don't see how this can be a
JavaFX bug given where it is crashing. FWIW, I haven't ever seen
anything like this.
-- Kevin
On 3/18/2022 10:25 AM, Philip Race wrote:
I think it is probable that this is a hotspot VM problem in the C2 JIT
compiler code.
I think it is probable that this is a hotspot VM problem in the C2 JIT
compiler code.
I've moved your bug report to hotspot :
https://bugs.openjdk.java.net/browse/JDK-8283386
The interesting question isn't about which version of FX used to work.
It is what was the last working version of the
Hi John, all,
Thanks for your detailed reply.
I submitted a bug report with detailed information.
- Run a different Java version
>
I tried different versions and vendors with the same result.
* OpenJDK 17.0.1
* Zulu 17.0.2
* I wanted to check also JDK18-ea but gradle does not yet support it
>
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
