-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: hs24, hs25
-
Component/s: hotspot
-
Environment:
There is chance that NMT can allocate memSnapshot object, but fail to initialize the object due to out of memory.
MemSnaphot object should be released in the situation.
-
b41
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8012064 | 8 | Zhengyu Gu | P4 | Closed | Fixed | b86 |
| JDK-8018101 | 7u45 | Zhengyu Gu | P4 | Closed | Fixed | b01 |
| JDK-8013073 | 7u40 | Zhengyu Gu | P4 | Closed | Fixed | b22 |
| JDK-8011670 | hs25 | Zhengyu Gu | P4 | Closed | Fixed | b27 |
- backported by
-
JDK-8011670 NMT: Memory leak when encountering out of memory error while initializing memory snapshot
-
- Closed
-
-
JDK-8012064 NMT: Memory leak when encountering out of memory error while initializing memory snapshot
-
- Closed
-
-
JDK-8013073 NMT: Memory leak when encountering out of memory error while initializing memory snapshot
-
- Closed
-
-
JDK-8018101 NMT: Memory leak when encountering out of memory error while initializing memory snapshot
-
- Closed
-