On Wed, 10 Nov 2021 08:47:10 GMT, Matthias Baesken <[email protected]> wrote:
>> I think Xcheck:jni raises a warning when two JNI calls are made in a row w/o >> calling exception check in between. So it is not necessary to have an actual >> exception to produce a warning. >> >> Probably it is reproduced there, because that system is "true" headless, and >> the execution code path is just different, or something like that, need to >> check what is the next/prev JNI call. >> Or maybe this method really throw an exception, need some more detail. > > Hello, in our central tests it was indeed a fastdbg OpenJDK. On my local > Windows 10 machine I could not reproduce it. > Our central tests run with -Djava.awt.headless=true , but I think the Win2019 > server machine itself is not headless . I could add a J2dTraceLn(J2D_TRACE_ERROR, . . . ) in case an exception occurs. The J2dTraceLn is already used at some other places in DWMIsCompositionEnabled so it might fit better than just ignoring the exception. ------------- PR: https://git.openjdk.java.net/jdk/pull/6306
