We do care at least about the first one (pending exceptions), and we should fix them. Can you file a bug?

As for the 'exceeds capacity' warning for JNI local refs we haven't in general cared about these (I don't know of any VM for which this would cause a problem), but we still might want to see if we can do something to silence these warnings.


Thanks.

-- Kevin


Scott Palmer wrote:
I noticed several warnings coming from javaFX when I ran my app with
-X:check:jni

Is that something worth filing an issue over,or is it basically a known
thing and we don't particularly care?

E.g.:

WARNING in native method: JNI call made without checking exceptions when
required to from CallStaticObjectMethodV
        at com.sun.glass.ui.win.WinDnDClipboard.push(Native Method)
        at
com.sun.glass.ui.win.WinSystemClipboard.pushToSystem(WinSystemClipboard.java:234)
        at com.sun.glass.ui.SystemClipboard.flush(SystemClipboard.java:51)
        at
com.sun.glass.ui.ClipboardAssistance.flush(ClipboardAssistance.java:59)
        at
com.sun.javafx.tk.quantum.QuantumClipboard.flush(QuantumClipboard.java:274)
        at
com.sun.javafx.tk.quantum.QuantumToolkit.startDrag(QuantumToolkit.java:1224)
        at
javafx.scene.Scene$DnDGesture.dragDetectedProcessed(Scene.java:2953)



WARNING: JNI local refs: zu, exceeds capacity: zu
        at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
        at
com.sun.glass.ui.win.WinApplication.lambda$null$148(WinApplication.java:191)
        at
com.sun.glass.ui.win.WinApplication$$Lambda$57/665296081.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
WARNING in native method: JNI call made without checking exceptions when
required to from CallStaticObjectMethodV
        at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
        at
com.sun.glass.ui.win.WinApplication.lambda$null$148(WinApplication.java:191)
        at
com.sun.glass.ui.win.WinApplication$$Lambda$57/665296081.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Regards,

Scott

Reply via email to