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

Default heap size causes native memory exhaustion on 32 bit Windows

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc
    • Introduced In Version:
      9
    • Resolved In Build:
      b137
    • Verification:
      Not verified

      Description

      Use the 32 bit windows fastdebug build from a current promoted build
      (eg b126 as used here) to run the standard SwingSet2 demo

      Click around in a couple of tabs and BOOM.
      It will die with an error message that amounts to insufficient memory.

      C:b126dbg\jdk-9\fastdebug\bin\java -jar SwingSet2.jar
      java.lang.OutOfMemoryError
      #
      # There is insufficient memory for the Java Runtime Environment to continue.
      # Native memory allocation (malloc) failed to allocate 566080 bytes for Chunk::n
      ew
      # An error report file with more information is saved as:
      # demo\jfc\SwingSet2\hs_err_pid5036.log
      #
      # Compiler replay data is saved as:
      # demo\jfc\SwingSet2\replay_pid5036.log

      This appears to be a regression from removing the client VM as builds
      pre-dating that work fine.

      I expect that this means that the 32 bit VM product build is also more
      likely to run out of memory in the same way - although it will take
      more than this demo to do it

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mgerdin Mikael Gerdin (Inactive)
                Reporter:
                prr Philip Race
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: