On Mac OS X, when returning from a sleep or hibernate state the JVM crashes frequently. This crash also occurs when an external monitor is unplugged or added.

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000123d5f027, pid=68362, tid=0x000000000000c107
#
# JRE version: Java(TM) 2 Runtime Environment, Standard Edition (8.0_201-b09)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.201-b09 mixed mode bsd-amd64
compressed oops)
# Problematic frame:
# C [libawt_lwawt.dylib+0x1c027] OGLSD_SetScratchSurface+0x49
#
# Failed to write core dump. Core dumps have been disabled. To enable core
dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Stack: [0x0000700010163000,0x0000700010263000], sp=0x0000700010262750, free
space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
code)
C [libawt_lwawt.dylib+0x1c027] OGLSD_SetScratchSurface+0x49
C [libawt_lwawt.dylib+0x3d5f2]
Java_sun_java2d_opengl_OGLRenderQueue_flushBuffer+0x63a
J 7431 sun.java2d.opengl.OGLRenderQueue.flushBuffer(JI)V (0 bytes) @
0x0000000113b7cbea [0x0000000113b7cb40+0xaa]
J 7171 C1 sun.java2d.opengl.OGLRenderQueue.flushBuffer()V (41 bytes) @
0x0000000113aa4abc [0x0000000113aa4860+0x25c]
J 7170 C1
sun.java2d.opengl.OGLRenderQueue.access$100(Lsun/java2d/opengl/OGLRenderQueue;
)V (5 bytes) @ 0x0000000113aa1ddc [0x0000000113aa1d80+0x5c]
j sun.java2d.opengl.OGLRenderQueue$QueueFlusher.run()V+81
v ~StubRoutines::call_stub
V [libjvm.dylib+0x2f0bea]
V [libjvm.dylib+0x2f138e]
V [libjvm.dylib+0x2f153a]
V [libjvm.dylib+0x34be29]
V [libjvm.dylib+0x570c33]
V [libjvm.dylib+0x57232e]
V [libjvm.dylib+0x48f3ca]
C [libsystem_pthread.dylib+0x32eb] _pthread_body+0x7e
C [libsystem_pthread.dylib+0x6249] _pthread_start+0x42
C [libsystem_pthread.dylib+0x240d] thread_start+0xd
C 0x0000000000000000

REPRODUCTION INSTRUCTIONS
-------------------------
The problem cannot be reproduced 100% reliably, but it happens frequently
enough to be reproduced within a reasonable timescale.

As mentioned above, the crash occurs when waking from sleep/hibernate or
after changing the monitor configuration.