JDK-8183100 is a fixed issue. But it basically undid the fix for https://bugs.openjdk.java.net/browse/JDK-8151756 <https://bugs.openjdk.java.net/browse/JDK-8151756> I think you mean to ask when JDK-8193445 might be addressed.
I too would like to see the performance return, and actually I’m hoping it can be made better than it was before. Performance improvements and a JNI mechanism to get at native window handles are the first two items on my wish list. Though extendable media support could potentially beat out the window handle thing.. I only need a native window handle so I can do native rendering of video frames from a non-JavaFX source. Scott > On Jan 17, 2019, at 8:05 AM, <[email protected]> > <[email protected]> wrote: > > Does anybody has any information about a target release for fixing > https://bugs.openjdk.java.net/browse/JDK-8183100 , this issue causing severe > performance degradation since JDK1.8.172? > > > > Since JDK1.8.182, CSS is applied redundantly, leading too significant > performance degradation, on scenes with many levels of hierarchy. > > > > I logged this issue in two JIRA in December 2018 (more than 1 year ago) : > > https://bugs.openjdk.java.net/browse/JDK-8193445 > > https://bugs.openjdk.java.net/browse/JDK-8209830 > > > > I've reported another issue https://bugs.openjdk.java.net/browse/JDK-8199216 > , showing performance and memory issue caused by Javafx PseudoClassState > objects. This issue could be related to the previous ones. > > > > This is a really BLOCKING issue, our product is stuck with JDK1.8.162, > blocking us for trying a migration to JDK10 or JDK11! > > > > Daniel Weil (ARGOSIM) >
