Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 9
    • Affects Version/s: 8u40, 9
    • Component/s: hotspot
    • b35
    • generic
    • generic
    • Not verified

        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.

              Assignee:
              Coleen Phillimore
              Reporter:
              Filipp Zhinkin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: