Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083083 | emb-9 | Coleen Phillimore | P3 | Resolved | Fixed | b35 |
JDK-8063333 | 8u45 | Coleen Phillimore | P3 | Resolved | Fixed | b01 |
JDK-8059642 | 8u40 | Coleen Phillimore | P3 | Closed | Fixed | b09 |
JDK-8071069 | emb-8u47 | Coleen Phillimore | P3 | Resolved | Fixed | team |
# Internal Error (mallocTracker.cpp:146), pid=4256, tid=3086310288
# fatal error: Should not use malloc for big memory block, use virtual memory instead
when someone is trying to allocate more then 1G of memory using Unsafe.allocateMemory still causing a fatal error on 32bit platforms.
- backported by
-
JDK-8063333 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms
-
- Resolved
-
-
JDK-8071069 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms
-
- Resolved
-
-
JDK-8083083 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms
-
- Resolved
-
-
JDK-8059642 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms
-
- Closed
-
- relates to
-
JDK-8055289 Internal Error: mallocTracker.cpp:146 fatal error: Should not use malloc for big memory block, use virtual memory instead
-
- Closed
-