JDK-8059104 : SIGSEGV VirtualMemoryTracker::remove_uncommitted_region
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 8u40
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2014-09-25
  • Updated: 2014-10-23
  • Resolved: 2014-10-23
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 :  
JDK-8059100 - SIGSEGV VirtualMemoryTracker::remove_released_region
Description
The hs_err head is:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000704c2c47, pid=23808, tid=22884
#
# JRE version: Java(TM) SE Runtime Environment (8.0_40-b07) (build 1.8.0_40-ea-b07)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.40-b11 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V  [jvm.dll+0x252c47]  VirtualMemoryTracker::remove_uncommitted_region+0x87
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x000000001ef0a000):  JavaThread "JDWP Command Reader" daemon [_thread_in_vm, id=22884, stack(0x0000000020060000,0x0000000020160000)]

siginfo: ExceptionCode=0xc0000005, reading address 0x0000000000000000

Registers:
RAX=0x0000000000000000, RBX=0x0000000000004000, RCX=0x0000000000000000, RDX=0x000000002015f4c0
RSP=0x000000002015f4a0, RBP=0x000000002015f6c0, RSI=0x0000000020060000, RDI=0x0000000020060000
R8 =0x0000000000004000, R9 =0x000000002015f6c0, R10=0x0000000000000000, R11=0x000000002015f528
R12=0x0000000000000000, R13=0x0000000000000000, R14=0x000000001ef0a000, R15=0x0000000000000000
RIP=0x00000000704c2c47, EFLAGS=0x0000000000010206

Top of Stack: (sp=0x000000002015f4a0)
0x000000002015f4a0:   0000000600000001 0000000000000000
0x000000002015f4b0:   0000000000000000 0000000072dd2865
0x000000002015f4c0:   0000000020060000 0000000000004000
0x000000002015f4d0:   0000000070865688 0000000000000000
0x000000002015f4e0:   0000000000000000 0000000000000000
0x000000002015f4f0:   0000000000000000 0000000000000000
0x000000002015f500:   0000000000000000 0000000000000000
0x000000002015f510:   000000000000000f 00000006dcfb8838
0x000000002015f520:   0000000000004000 00000000704bdf1b
0x000000002015f530:   000000002015f5a0 0000000020060000
0x000000002015f540:   00000006dcfb8838 000000001eeef328
0x000000002015f550:   0000000000004000 00000000704728b8
0x000000002015f560:   0000000000000001 0000000020060000
0x000000002015f570:   0000000000000000 000000001eeef328
0x000000002015f580:   000000001ef0a000 0000000070491807
0x000000002015f590:   0000000020060000 0000000000000000 

Instructions: (pc=0x00000000704c2c47)
0x00000000704c2c27:   85 d9 57 00 49 89 43 d8 48 8b 05 82 d9 57 00 49
0x00000000704c2c37:   89 43 e0 c7 44 24 70 0f 00 00 00 c6 44 24 74 00
0x00000000704c2c47:   48 8b 01 ff 50 28 4c 8b c3 48 8b d7 48 8b c8 e8
0x00000000704c2c57:   e5 f4 ff ff 48 8b 5c 24 38 48 c7 44 24 38 00 00 


Register to memory mapping:

RAX=0x0000000000000000 is an unknown value
RBX=0x0000000000004000 is an unknown value
RCX=0x0000000000000000 is an unknown value
RDX=0x000000002015f4c0 is pointing into the stack for thread: 0x000000001ef0a000
RSP=0x000000002015f4a0 is pointing into the stack for thread: 0x000000001ef0a000
RBP=0x000000002015f6c0 is pointing into the stack for thread: 0x000000001ef0a000
RSI=0x0000000020060000 is an unknown value
RDI=0x0000000020060000 is an unknown value
R8 =0x0000000000004000 is an unknown value
R9 =0x000000002015f6c0 is pointing into the stack for thread: 0x000000001ef0a000
R10=0x0000000000000000 is an unknown value
R11=0x000000002015f528 is pointing into the stack for thread: 0x000000001ef0a000
R12=0x0000000000000000 is an unknown value
R13=0x0000000000000000 is an unknown value
R14=0x000000001ef0a000 is a thread
R15=0x0000000000000000 is an unknown value


Stack: [0x0000000020060000,0x0000000020160000],  sp=0x000000002015f4a0,  free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0x252c47]  VirtualMemoryTracker::remove_uncommitted_region+0x87
V  [jvm.dll+0x24df1b]  Tracker::record+0x9b
V  [jvm.dll+0x2028b8]  os::uncommit_memory+0x78
V  [jvm.dll+0x221807]  JavaThread::remove_stack_guard_pages+0x47
V  [jvm.dll+0x227504]  JavaThread::exit+0x724
V  [jvm.dll+0x2286ad]  JavaThread::thread_main_inner+0xed
V  [jvm.dll+0x27aaba]  java_start+0x8a
C  [msvcr100.dll+0x21d9f]
C  [msvcr100.dll+0x21e3b]
C  [kernel32.dll+0x159ed]
C  [ntdll.dll+0x2c541]
Comments
This is the same issue as the other bug. This test runs to completion and does PrintNMTStatistics, which used to set the tracking level to minimal. Another thread overflows and sets the tracking level to summary and another thread, as it exits tries to get the reserved regions, which have been deleted. There are a lot of threads in this test, which is probably why the symptom was different.
23-10-2014