Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8058818

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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P3
    • 9
    • 8u40, 9
    • hotspot
    • b35
    • generic
    • generic
    • Not verified

    Backports

      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.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8063333 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8071069 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8083083 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8059642 Allocation of more then 1G of memory using Unsafe.allocateMemory is still causing a fatal error on 32bit platforms

            • P3 - Major loss of function.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8055289 Internal Error: mallocTracker.cpp:146 fatal error: Should not use malloc for big memory block, use virtual memory instead

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Closed

            Activity

              People

                coleenp Coleen Phillimore
                fzhinkin Filipp Zhinkin
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: