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

Do not use FLAG_SET_ERGO to update MaxRAM for emulated client

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P2
    • 9
    • 9, 10
    • hotspot
    • b163
    • Verified

    Backports

      Description

        setting MaxRAM FLAG_SET_ERGO affects Arguments::set_heap_size inappropriately,

        void Arguments::set_heap_size() {
          julong phys_mem =
            FLAG_IS_DEFAULT(MaxRAM) ? MIN2(os::physical_memory(), (julong)MaxRAM)
                                    : (julong)MaxRAM;

        so, do not use FLAG_SET_ERGO to update MaxRAM for emulated client

        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-8178202 Do not use FLAG_SET_ERGO to update MaxRAM for emulated client

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8166002 Emulate client build on platforms with reduced virtual address space

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Activity

              People

                jcm Jamsheed C M (Inactive)
                jcm Jamsheed C M (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: