Hey Anthony,
could you please check whether bug report with review id JI-9014446 was also
closed, because nobody was able to reproduce it?
If so, the bug also re-appeared in the final Java 8_u20.
It seems to be connected to a message in standard error:
exception in QueueFlusher:
java.lang.RuntimeException: Non-Java exception raised, not handled! (Original
problem: -[__NSTaggedDate view]: unrecognized selector sent to instance
0xbadd9a48d2ccbead)
at sun.java2d.opengl.OGLRenderQueue.flushBuffer(Native Method)
at sun.java2d.opengl.OGLRenderQueue.flushBuffer(OGLRenderQueue.java:148)
at sun.java2d.opengl.OGLRenderQueue.access$100(OGLRenderQueue.java:41)
at
sun.java2d.opengl.OGLRenderQueue$QueueFlusher.run(OGLRenderQueue.java:226)
A new, corresponding crash log for OS X 10.9.4 can be found at
http://www.beatunes.com/download/oglflusher.crash
The key part being:
Thread 23 Crashed:: Java: Java2D Queue Flusher
0 libsystem_kernel.dylib 0x00007fff8cddf866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8778335c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff8e272b1a abort + 125
3 libjvm.dylib 0x0000000107720b07 os::abort(bool) + 25
4 libjvm.dylib 0x000000010783cd26
VMError::report_and_die() + 2260
5 libjvm.dylib 0x000000010772267a
JVM_handle_bsd_signal + 1131
6 libjvm.dylib 0x000000010771eb3b signalHandler(int,
__siginfo*, void*) + 47
7 libsystem_platform.dylib 0x00007fff8e1555aa _sigtramp + 26
8 libawt_lwawt.dylib 0x000000017f99d4cc
OGLSD_SetScratchSurface + 51
9 libawt_lwawt.dylib 0x000000017f9bd5ae
Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer + 1594
10 ??? 0x0000000109530a6a 0 + 4451404394
11 ??? 0x0000000108afac44 0 + 4440697924
To the untrained eye, the stacktrace combined with the crash log seem to
indicate that the call
if ([ctxinfo->context view] == nil) {
in OGLContext * OGLSD_SetScratchSurface(JNIEnv *env, jlong pConfigInfo) of
macosx/native/libawt_lwawt/sun/java2d/opengl/CGLSurfaceData.m somehow calls
"view" on a bad pointer. Perhaps some more sanity checks are in order before
calling "view".
In any case, I would appreciate it, if you attached this info to the original
bug, and if it was closed already, re-opened it.
Thank you,
-hendrik
