JDK-6392973 : EXCEPTION_ACCESS_VIOLATION error displayed in Bigapps vtest on Windows2003
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2_12
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_2003
  • CPU: x86
  • Submitted: 2006-03-02
  • Updated: 2014-02-27
  • Resolved: 2006-05-24
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.
Other
1.4.2_13Resolved
Related Reports
Relates :  
JDK-6409422 - EXCEPTION_ACCESS_VIOLATION coming to a safepoint?
Relates :  
JDK-6177677 - VolanoMark bigapp is failing on win2003 EE with 1.4.2_X
Description
Steps to reproduce:

Find a Windows 2003 machine (x86) without Service Pack 1 installed.

Run Bigapps vtest, see test procedure document:

http://jqa.ireland/procedures/test_procedures/all_test_procedures/BigApps.html

After a couple of hours running an EXCEPTION_ACCESS_VIOLATION GUI appears and an error log is created.  See attached log.

This only occurs when SP1 is NOT installed but some of our customers may not have SP1 so this CR is being created as a reference.
Further Investigation:

1.4.2-b28 - error doesnt occur
1.4.2_06  - error doesnt occur
1.4.2_07  - error doesnt occur
1.4.2_08  - error occurs
1.4.2_11b6 - error occurs

Looks like this only started happening from 1.4.2_08 onwards.
Comments
EVALUATION This is a failure during young generation collection. VM_Operation (0x086ffad0): generation collection for allocation, mode: safepoint, requested by thread 0x0406aec8 Eden is 100% full; allocation attempt was made in eden, that failed and collection was invoked. eden space 832K, 100% used [0x10010000, 0x100e0000, 0x100e0000) Requies further investingation to find cause of this issue.
28-03-2006