After several hours of immersion in jfxrt.jar , trial and error and using @NwDx, here is a brief description of what is happening.
The Gradle build system works with the root JUL logger and sets the default FINER level to FINER from the source INFO . This activates many of the internal mechanisms inside the JavaFX runtime. Most noticeably:
- Clip area debugging dependent on JUL Logger
PerfLogger Some JUL Logger Levels- many other unnecessary protocols, possibly for / dev / null
If you are careless, you can use: LogManager.getLogManager().reset() to fix everything. More careful patients may continue to read.
Click Area Debugging
There is visual debugging code protected by log.isLoggable(Level.FINE) in com.sun.webpane.sg.prism.WCGraphicsPrismContext .
This is a known bug registered here: https://bugs.openjdk.java.net/browse/JDK-8096483 Looking at the fix version: everyone up to 1.8.0u40 is susceptible to this unwanted visual debugging (see the table in the question). In 1.8.0u40 + you can -Dcom.sun.webkit.debugDrawClipShape=true enable this "function".
To be safe, you should turn off logging for this class either by configuring JUL, or:
String name = com.sun.webpane.sg.prism.WCGraphicsPrismContext.class.getName(); java.util.logging.Logger.getLogger(name).setLevel(java.util.logging.Level.OFF);
PerfLogger Logging
As mentioned in this question, some diagnostic data is spit out in stdout. PerfLogger checks the FINE level . The source of these messages is as follows:
com.sun.webpane.perf.WCGraphicsPerfLoggercom.sun.webpane.perf.WCFontPerfLoggercom.sun.webpane.platform.Invoker named LocksTextBreakIteratorJava in jfxwebkit.dll is called XXXX via LOG_PERF_RECORD
... someone literally took an example, why ?: (
The easiest way to disable this:
java.util.logging.Logger.getLogger('com.sun.webpane.perf').setLevel(Level.OFF)
because the package name is hard-coded or Logger instances are in that package.
Other
It is probably worth making the log level higher (INFO-OFF) for all com.sun.* And javafx.* to prevent further strangeness or performance degradation.
For more information, see our chat .