Hotspot crash when trying to allocate array exceeding VM limit

Problem Description : nsk/stress/except/ test cases fail due to memory issues

Tested_Java_Release : 1.6.0
Tested_Build : B58
Operating System : generic
Test cases : nsk/stress/except/except001
: nsk/stress/except/except002
: nsk/stress/except/except003
: nsk/stress/except/except004
: nsk/stress/except/except005
: nsk/stress/except/except006
: nsk/stress/except/except007
: nsk/stress/except/except008
: nsk/stress/except/except009
: nsk/stress/except/except010
: nsk/stress/except/except011
: nsk/stress/except/except012
: nsk/stress/memory/memleak005
: nsk/stress/memory/memleak007


Results Location : http://vmsqe.sfbay/nightly/mantis/DTWS/results/10-22-05/ClientVM/solx86/mixed/Main_Baseline/nsk.stress-NIGHTLY-Main_Baseline-ClientVM-mixed-solx86-2005-10-23-03-06-25/analysis.html

Error Message : See Below

#annotate TEST javaopt=-client -Xmixed
/net/vmsqe.sfbay/export/nightly/mantis/JDK/baseline/jdk1.6/solaris-i586/bin/java -client -Xmixed -DHANGINGJAVA11293 except012
##Exit status of execution step=6
##Core file exists
##!checkExitCode

## While printing this message, JVM seems to initiate the output
## stream, so that it will not need more memory to print later,
## when the heap would fail to provide more memory.
##
## Note, that the test maintains especial static log[] field in
## order to avoid printing when the heap seems exhausted.
## Nevertheless, printing could arise OutOfMemoryError even
## after all the memory allocated by the test is released.
##
## That problem is caused by the known JDK/HotSpot bugs:
## 4239841 (P1/S5) 1.1: poor garbage collector performance
## 4245060 (P4/S5) poor garbage collector performance
##
## This message is just intended to work-around that problem.
## If printing should fail even so, the test will try to return
## the exit status 96 instead of 97 to indicate the problem.
## However, the test may fail or even crash on some platforms
## suffering the bug 4239841 or 4245060.
##
## An unexpected error has been detected by Java Runtime Environment:
##
## SIGSEGV (0xb) at pc=0xdecd9464, pid=13565, tid=1
##
## Java VM: Java HotSpot(TM) Client VM (20051021085710.ysr.dragon mixed mode)
## Problematic frame:
## V [libjvm.so+0xa9464]