| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8317861 | 8u401 | Daniel Skantz | P3 | Resolved | Fixed | b03 |
os::check_heap seems to be buggy on Windows (see JDK-8147481, JDK-8148813, JDK-8147481).
We have actually never fixed an actual bug with os::check_heap(). All we see are (a) bugs inside the implementation of os::check_heap(), (b) seemingly bugs inside HeapValidate() and (c) unreproducible crashes which are probably because of (b):
https://bugs.openjdk.java.net/issues/?jql=text%20~%20%22os%3A%3Acheck_heap%22
So instead of spending useless efforts for checking the heap dump, we should disable this feature with a develop flag, such as UseOSHeapChecking.
We have actually never fixed an actual bug with os::check_heap(). All we see are (a) bugs inside the implementation of os::check_heap(), (b) seemingly bugs inside HeapValidate() and (c) unreproducible crashes which are probably because of (b):
https://bugs.openjdk.java.net/issues/?jql=text%20~%20%22os%3A%3Acheck_heap%22
So instead of spending useless efforts for checking the heap dump, we should disable this feature with a develop flag, such as UseOSHeapChecking.
- backported by
-
JDK-8317861 Remove os::check_heap on Windows
-
- Resolved
-
- relates to
-
JDK-8163015 Windows os::check_heap() fails with fatal error: corrupted C heap
-
- Closed
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-