-
Bug
-
Resolution: Fixed
-
P4
-
6
-
b01
-
generic
-
generic
The +HeapDumpOnOutOfMemoryError option was back-ported to 1.4.2_12 via 6280629-
Unfortunately the changes to the object iteration implementation in the through-put collector weren't included in the putback so it means that this option doesn't work with +UseParallelGC. One customer reports this guarantee:
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (504152414C4C454C33434156454E4745284541500E43505001E1
01), pid=24538, tid=6
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_12-b02 mixed mode)
The error ID points to parallelScavengeHeap.cpp, line 481, which is the
following function:
void ParallelScavengeHeap::object_iterate(ObjectClosure* cl) {
Unimplemented();
}
This is easy to fix and should be fixed in the next available 1.4.2_xx update.
Unfortunately the changes to the object iteration implementation in the through-put collector weren't included in the putback so it means that this option doesn't work with +UseParallelGC. One customer reports this guarantee:
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (504152414C4C454C33434156454E4745284541500E43505001E1
01), pid=24538, tid=6
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_12-b02 mixed mode)
The error ID points to parallelScavengeHeap.cpp, line 481, which is the
following function:
void ParallelScavengeHeap::object_iterate(ObjectClosure* cl) {
Unimplemented();
}
This is easy to fix and should be fixed in the next available 1.4.2_xx update.