Kevin Rushforth

This GitHub issue tracker is not actively tracked or managed. Please file a bug at [bugreport.java.com](https://bugreport.java.com/).

> Moreover, there are many spacing changes, such as in D3DContext.java and I'm not sure at all these are within the style conventions of OpenJFX. Kevin would have to comment...

As announced in [this message](https://mail.openjdk.java.net/pipermail/openjfx-dev/2019-September/023551.html), the official `jfx` repository is moving from [hg.openjdk.java.net/openjfx/jfx-dev/rt](https://hg.openjdk.java.net/openjfx/jfx-dev/rt) to [github.com/openjdk/jfx](https://github.com/openjdk/jfx). This [sandbox repository](https://github.com/javafxports/openjdk-jfx) is being retired on 1-Oct-2019. You will need to migrate your WIP...

This has now been transferred to the JDK project in JBS as [JDK-8229751](https://bugs.openjdk.java.net/browse/JDK-8229751).

https://bugs.openjdk.java.net/browse/JDK-8225574

> I guess dirty nodes were modified by another thread? Possibly, in which case it would be an application bug. Nodes that are "live" (attached to a scene of a...

The thread is only checked for Window and Scene operations. Modifying scene graph nodes does not check the thread, but is documented (in the class documentation for Node) as needing...

Do you have any bindings where the source of the binding might be operated on by another thread? If you can provide a test program, then we could also take...

I see. In that case this will be hard to diagnose. Another approach would be for you to instrument a local build of JavaFX and add a thread check in...

Thanks for the test case. If the above code is causing the AIOOBE then it isn't a threading problem. As for a fix...we would need to understand the problem first...