On Fri, 12 Nov 2021 07:59:21 GMT, Matthias Baesken <mbaes...@openjdk.org> wrote:
>> Before ignoring an exception it is better to check why the warning was >> raised, if that warning is correct then we should try to propogate/report >> exception to the app, if it is not possible then we should use trace macro. > > Hello, I added a trace call. This is similar to what is done in > https://github.com/openjdk/jdk/blob/master/src/java.desktop/windows/native/libawt/java2d/d3d/D3DRenderQueue.cpp#L869 > . In the old fix the trace was added there because that method is executed in the infinite loop on some special thread, so an exception could not be thrown to the user, is it the case in the current issue? ------------- PR: https://git.openjdk.java.net/jdk/pull/6306
