JDK-6886827 : Application crash while running many swing applications in parallel
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6u14
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2009-09-30
  • Updated: 2010-08-19
  • Resolved: 2009-10-21
Related Reports
Duplicate :  
JDK-6788497 - D3D: stability issues in low video memory situations
Description
Our team develops java client GUI applications (swing) running on Windows workstations. Recently several engineers are experiencing unexpected crashes of the JVM.

It usually happens when more than one instance of application is running on the station (multiple JVMs) but with no other specific scenario or stress applied.

You can find all the information of JVM, system, environment in the attached error report.

Error log summary:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d0e4866, pid=3704, tid=13080
#
# JRE version: 6.0_14-b08
# Java VM: Java HotSpot(TM) Client VM (14.0-b16 mixed mode windows-x86 )
# Problematic frame:
# C  [awt.dll+0x34866]
#

Please find attached several crash logs:

<<hs_err_pid3704.log>> <<hs_err_pid27084.log>> <<hs_err_pid26732.log>> <<hs_err_pid23516.log>> <<hs_err_pid17324.log>> <<hs_err_pid23696.log>> <<hs_err_pid27920.log>>


Thank you,
Gilad Tzeelon
Cisco Systems, Inc.
Sun Partner Advantage Program company id: *IL1000123*
Comments
EVALUATION Unfortunatelly attached crash logs are empty and it hard to guess real root cause. However, it appears to be another manifestation of 6788497. If amount of video memory is not sufficient then d3d pipeline might start behave weird - sometimes we can not detect that memory is not available and fail when we try to use "allocated" memory, somtimes we acutally catch OOM but can not handle it gracefully. I'll close this bug report as duplicate of 6788497. Please feel free to attach additional details to that report. In particular: - what is graphics hardware used (video board, memory on board, drivers version) - run your application with set J2D_TRACE_LEVEL=4 and see if there are any warnings/errors before crash - check how much video memory is available (manufacturer of your board might have tools available, e.g. nvidia perfhud) See also http://java.sun.com/javase/6/webnotes/trouble/TSG-Desktop/html/java2d.html
21-10-2009
EVALUATION The crash looks similar to 6893677. The header of the log ([awt.dll+0x34866]) refers to IntRgbToIntArgbPreConvert (src/windows/native/sun/java2d/d3d/D3DBlitLoops.cpp) owned by Java2D team. Transferring to Java2D team for initial evaluation.
21-10-2009