There is a testcase in the reliability testsuite which tests setting cursors to different AWT components. It calls the Cursor(int type) constructor in each iteration to create the cursor and sets it to the component. The testcase will be run for a long time and Cursor constructor will be called a very high number of times. This resulted in a JVM crash in Solaris and a hang in Linux. The testcase slows down and prints out the following message repeatedly before crashing:

Xlib: resource ID allocation space exhausted!

Log of the crash attached.

Workaround: The testcase was modified in such a way that the Cursor(int type) constructor was not repeatedly called. During the test startup, some cursors are constructed and reused. Now the crash does not occur.