JDK-8143249 : "fatal error: corrupted C heap" with '-XX:MallocVerifyInterval=1' option on win-64
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Not an Issue
  • OS: windows
  • Submitted: 2015-11-18
  • Updated: 2016-02-02
  • Resolved: 2016-02-02
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 9
9Resolved
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
During testing of modified runtime/CommandLine/OptionsValidation/TestOptionsWithRanges.java test for JDK-8143038 I hit fatal error for windows-amd64 when ran JVM with '-XX:MallocVerifyInterval=1' option:
"C heap has been corrupted (time: 1163 allocations)
corrupted block near address 0x2a889190, length 1168
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=\\os_windows.cpp:5270
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (C:\\jprt\\T\\P1\\143211.dmitry\\s\\hotspot\\src\\os\\windows\\vm\\os_windows.cpp:5270), pid=89544, tid=45092
#  fatal error: corrupted C heap
#
# JRE version:  (9.0) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.9.0-internal-20151117143211.dmitry.jdk9-hs-rt-b00, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)
# Core dump will be written. Default location: C:\\Users\\aurora\\sandbox\\results\\workDir\\runtime\\CommandLine\\OptionsValidation\\TestOptionsWithRanges\\hs_err_pid89544.mdmp
#
# An error report file with more information is saved as:
# C:\\Users\\aurora\\sandbox\\results\\workDir\\runtime\\CommandLine\\OptionsValidation\\TestOptionsWithRanges\\hs_err_pid89544.log
#
..."

hs_err_pid89544.log is attached.

The following revision of source code with test-only changes was used:
1) hotspot repo
changeset:   9402:23afa049ffd8
tag:         tip
user:        dholmes
date:        Mon Nov 16 18:50:55 2015 -0500
summary:     8139300: Internal Error (vm/utilities/debug.cpp:399), # Error: ShouldNotReachHere()

2) hotspot/src/closed repo
changeset:   1913:c9df21bae670
tag:         tip
parent:      1912:7ccba55decbf
parent:      1910:fe152f6b9103
user:        amurillo
date:        Fri Nov 13 10:35:26 2015 -0800
summary:     Merge
Comments
Likely a Windows internal bug in HeapWalk/HeapValidate. Not a HotSpot bug and no indication of actual heap error. See details in JDK-8147481.
02-02-2016

Probably, the same problem as in JDK-8069282
18-11-2015