JDK-8058818 : Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 8u40,9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2014-09-19
  • Updated: 2015-06-03
  • Resolved: 2014-09-25
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 8 JDK 9
8u40Fixed 9 b35Fixed
Related Reports
Relates :  
JDK-8055289 - Internal Error: mallocTracker.cpp:146 fatal error: Should not use malloc for big memory block, use virtual memory instead
Description
Even after integration of JDK-8055289 JVM crashes with:

#  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.

JDK-8055289 preserves us from such issue only when NMT is on, but MallocTracker::record_malloc is called even if NMT is off.