Print crash observed under openJDK

[Lewis Rosenthal]

[will cross ref this to openJDK bug list]

Using either openJDK GA2 or GA3 with Odin 0.8.5, printing causes the application to exit. A blank page is ejected from the printer. Printing is to an HP LaserJet, using the Postscript driver, printing via LPR.

Rolling back to Odin 0.8.4 (and using openJDK GA2), printing works as expected.

Note JVM crash log (full log attached):

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x15429a07, pid=156, tid=10223635
#
# JRE version: 6.0-b24
# Java VM: OpenJDK Client VM (20.0-b12 mixed mode os2-x86 )
# Problematic frame:
# C  [WGSS50+0x9a07]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[Lewis Rosenthal]

Crash log from Moneydance 2011

[dmik]

What if you use GA3 and Odin 0.8.5?

[Lewis Rosenthal]

Per my initial description, using either openJDK GA2 or GA3 with Odin 0.8.5 results in this condition, which is what has led me to believe that the problem is with Odin and not with Java.

[Lewis Rosenthal]

Confirming that hotfix_ga3_1-20120807.zip for openJDK 6 b25 GA3 has *no* effect on this issue (crash still occurs).

[Lewis Rosenthal]

This problem is still present through Odin 0.8.8. Presently, I'm stuck at Odin 0.8.4 and the last Java build which ran on that.

[Lewis Rosenthal]

Current log file of crash (Odin 0.8.8, Java 1.6 GA4)

[dmik]

This must also be the reason for ​http://svn.netlabs.org/java/ticket/206 (as well as for ​http://svn.netlabs.org/java/ticket/178).

[dmik]

The problem has been fixed in r22062 (see commit msg). This is a regression of r21998.

The test from Java ticket 206 now works well.

[Lewis Rosenthal]

What I can confirm at this time is that installing Odin 0.8.8 and back-leveling gdi32.dll to 0.8.4 works around the issue, so it looks like this was indeed the culprit. Looking forward to a release of 0.8.9.

Thanks so much!