JDK-8058251 : assert(_count > 0) failed: Negative counter when running runtime/NMT/MallocTrackingVerify.java
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 8u40,9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-09-11
  • Updated: 2015-06-03
  • Resolved: 2014-11-06
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 8 JDK 9
8u40Fixed 9 b40Fixed
Related Reports
Blocks :  
Relates :  
Relates :  
Description
Seen in jprt:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (C:\jprt\T\P1\163041.mikael\s\hotspot\src\share\vm\services/mallocTracker.hpp:72), pid=5432, tid=8032
#  assert(_count > 0) failed: Negative counter
#
# JRE version: Java(TM) SE Runtime Environment (9.0) (build 1.9.0-internal-fastdebug-201409111630.mikael.hs-rt-b00)
# Java VM: Java HotSpot(TM) Client VM (1.9.0-internal-201409111630.mikael.hs-rt-b00 mixed mode 
windows-x86 )

# Core dump written. Default location: C:\jprt\T\P1\163041.mikael\s\hotspot\build\windows-i586\testoutput\JTwork\runtime\NMT\MallocTrackingVerify\hs_err_pid5432.mdmp
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#


13aafa38 737d6c52 00000028 00000032 00000000 jvm!MallocSiteTable::deallocation_at+0x59 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\services\mallocsitetable.hpp @ 221]
13aafa4c 737d6d99 13caeb48 13aafa94 737918d3 jvm!MallocHeader::release+0x82 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\services\malloctracker.cpp @ 84]
13aafa58 737918d3 13caeb48 13caeb48 73a2fae0 jvm!MallocTracker::record_free+0x49 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\services\malloctracker.cpp @ 197]
13aafa94 73794e9f 13caeb48 00000007 012ef9ec jvm!os::free+0x73 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\os.cpp @ 717]
13aafaac 737951a0 73781b95 737c6327 13cbe400 jvm!PerfDataManager::destroy+0xbf [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\perfdata.cpp @ 287]
13aafab0 73781b95 737c6327 13cbe400 737c63d6 jvm!perfMemory_exit+0x20 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\perfmemory.cpp @ 80]
13aafab4 737c6327 13cbe400 737c63d6 00000000 jvm!exit_globals+0x15 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\init.cpp @ 157]
13aafabc 737c63d6 00000000 012ef9ec 739e4bc4 jvm!VM_Exit::doit+0x17 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\vm_operations.cpp @ 452]
13aafaec 737c545e 00000000 13cbe400 73a00f9c jvm!VM_Operation::evaluate+0x76 [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\vm_operations.cpp @ 64]
13aafb6c 737c593e 012ef9ec 00016003 13cbe400 jvm!VMThread::evaluate_operation+0xbe [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\vmthread.cpp @ 357]
13aafcdc 737c5c2e 13cbe400 13aafd38 77d5fac9 jvm!VMThread::loop+0x38e [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\vmthread.cpp @ 475]
13aafd08 7382062e 00000000 00000001 738205c6 jvm!VMThread::run+0xae [c:\jprt\t\p1\163041.mikael\s\hotspot\src\share\vm\runtime\vmthread.cpp @ 270]
13aafd4c 73d5c556 13cbe400 1baed8a9 00000000 jvm!java_start+0xce [c:\jprt\t\p1\163041.mikael\s\hotspot\src\os\windows\vm\os_windows.cpp @ 449]

Comments
Agreed - if it's @ignored the prio should be lowered.
17-09-2014

I don't think this should be P1. It's intermittent and it is now @ignored and I can't reproduce it.
16-09-2014

I just observed this same problem on linux_i586. This failure will be blocking pushes when we switch to full JDK JPRT push jobs, and needs to be addressed immediately.
15-09-2014