I've been exchanging mail with a customer who has an application that runs
5.0 but does not run on a recent Peabody/mustang snapshot.
vm_info: Java HotSpot(TM) Client VM (1.6.0-rc-b71) for
windows-x86, built on Feb 9 2006 00:35:36 by
"java_re" with unknown MS VC++:1310
The error is
#
> # An unexpected error has been detected by Java
> Runtime Environment:
> #
> # java.lang.OutOfMemoryError: requested 83886080
> bytes for GrET in
C:\BUILD_AREA\jdk6\hotspot\src\share\vm\utilities\growableArray.cpp.
>> Out
>> of swap space?
The customer originally ran on both 5.0 and 6.0 with a 1.6g heap. The
5.0 works and the 6.0 does not. I asked the customer to reduce the
heap to 1.3g with the expectation that a smaller heap would leave
enough additional space free for other VM needs but the 6.0 still fails.
Attached is the last mail with some GC log output and the hs_err output.
5.0 but does not run on a recent Peabody/mustang snapshot.
vm_info: Java HotSpot(TM) Client VM (1.6.0-rc-b71) for
windows-x86, built on Feb 9 2006 00:35:36 by
"java_re" with unknown MS VC++:1310
The error is
#
> # An unexpected error has been detected by Java
> Runtime Environment:
> #
> # java.lang.OutOfMemoryError: requested 83886080
> bytes for GrET in
C:\BUILD_AREA\jdk6\hotspot\src\share\vm\utilities\growableArray.cpp.
>> Out
>> of swap space?
The customer originally ran on both 5.0 and 6.0 with a 1.6g heap. The
5.0 works and the 6.0 does not. I asked the customer to reduce the
heap to 1.3g with the expectation that a smaller heap would leave
enough additional space free for other VM needs but the 6.0 still fails.
Attached is the last mail with some GC log output and the hs_err output.