JDK-6645511 : crash in the sun_dc_pr_PathStroker_dispose
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: x86
  • Submitted: 2007-12-26
  • Updated: 2011-01-19
  • Resolved: 2008-06-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u10 b26Fixed 7Fixed
Description
FULL PRODUCT VERSION :
java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Linux geo 2.6.21.6 #1 SMP Fri Nov 16 14:39:24 EST 2007 x86_64 AMD Opteron(tm) Processor 246 AuthenticAMD GNU/Linux

EXTRA RELEVANT SYSTEM CONFIGURATION :
Headless machine

A DESCRIPTION OF THE PROBLEM :
Our web gis server, GeoServer, the jvm randomly crashes on the above box while trying to render maps on a graphics context.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
The problem occurs randomly. We don't have a specific way to reproduce it consistently.


ERROR MESSAGES/STACK TRACES THAT OCCUR :

*** glibc detected *** /opt/sun-java-1.6.0//bin/java: double free or corruption (!prev): 0x00002aaad8671150 ***
======= Backtrace: =========
/lib/libc.so.6[0x2b2543b03aad]
/lib/libc.so.6(cfree+0x76)[0x2b2543b05796]
/opt/actual/jdk1.6.0_03/jre/lib/amd64/libdcpr.so[0x2aaaddae0b4d]
/opt/actual/jdk1.6.0_03/jre/lib/amd64/libdcpr.so(Java_sun_dc_pr_PathStroker_dispose+0x71)[0x2aaaddae4e31]
[0x2aaaab8cbc85]

I can provide a fuller listing with all the libs and jars involved.

REPRODUCIBILITY :
This bug can be reproduced often.

Comments
EVALUATION Fixed by adding the check suggested by IBM
29-05-2008