On Tue, 9 Nov 2021 20:51:30 GMT, Sergey Bylokhov <s...@openjdk.org> wrote:
>> Yeah this looks like the wrong fix. >> -Xcheck:jni only warns like this if there are actual exceptions, doesn't it ? >> So if we had one, where was it ? >> >> Note that Windows Server 2019 is a staple of the CI testing at Oracle and >> the test hasn't failed in the > 2 months since it was integrated, so I'm >> wondering why it fails in your case ? >> Was this a debug build perhaps ? > > 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 . ------------- PR: https://git.openjdk.java.net/jdk/pull/6306
