stan/jdk-24
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

8028749: java -version crashes with 'fatal error: heap walk aborted with error 1'

Browse Source 
Check_heap() should only call HeapWalk() when HeapLock() is successful.

Reviewed-by: ctornqvi, sla, dcubed
This commit is contained in:
Ron Durbin 2014-05-15 10:44:20 -07:00
parent ca501f6b00
commit 54da05d840
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
hotspot/src/os/windows/vm/os_windows.cpp
View File

@ -5005,7 +5005,11 @@ bool os::check_heap(bool force) {
// wrong; at these points, eax contains the address of the offending block (I think).
// To get to the exlicit error message(s) below, just continue twice.
HANDLE heap = GetProcessHeap();
{ HeapLock(heap);
// If we fail to lock the heap, then gflags.exe has been used
// or some other special heap flag has been set that prevents
// locking. We don't try to walk a heap we can't lock.
if (HeapLock(heap) != 0) {
PROCESS_HEAP_ENTRY phe;
phe.lpData = NULL;
while (HeapWalk(heap, &phe) != 0) {