JDK-6394247 : Random VM crashes while printing
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 5.0u6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2006-03-06
  • Updated: 2010-05-12
  • Resolved: 2006-04-20
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
Full problem description:


Our Customer is developing software to maintain aircrafts.Their customers are over 35 airlines together using thousands of client-installations.Since they switched to Java5, they have massive problems printing out documents.Unfortunately ther did not notice the problem in their testing-process - so now they have this buggy version already installed 
in productive environments and a big pressure of thier customers to solve this issue.


While printing out documents (mostly large documents, up to 300 pages) the complete VM crashes in about 80% of the cases. Sometimes it happens after printing 10 pages, sometimes after 100 and it crashes on different positions inside the native code. 
This happens on all installations. In all cases, they have exceptions inside the native code, their application closes immediately.The problem happens in all patch-levels of 1.5.0. All JVM-parameters regarding JIT or JNI do not help - the only solution they found
until now is to switch back to 1.4.2 - there to problem does not occur at all.

Comments
EVALUATION The bug has been confirmed by the customer to be resolved by a 5.0 backport of the mustang fix for 6186524: Swing Basher throws an expection(EXCEPTION_ACCESS_VIOLATION) It further appears that several bugs : 4924298: Prints some (complex) pages incompletely 6308772: Landscape printing problem - VM crash or incomplete print are also manifestations of the same.
20-04-2006

WORK AROUND VM crashes only appear if the PC supports Hyper-Threading. For that, the workaround is to turn off Hyper-Threading in the BIOS of the PC.After that, the crashes are not reproduceable any more. Nevertheless this workaround is not very practicable for our customers.
06-03-2006