Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4600

Memory leak caused by ByteBufferSlicePool usage

    XMLWordPrintable

Details

    • Hide
      • Configure -XX:MaxDirectMemorySize=16M for server to hit error earlier . E.g. add into JAVA_OPTS of standalone.conf
      • run server
      • Run this reproducer
        loop.sh
        #!/bin/bash
for i in {1..10000}
do
  echo $i
  ${jboss.home}/bin/jboss-cli.sh -c ":reload"
  if [ $? == 1 ]
  then
      break
  fi
done

      Eventually you will get an OutOfMemoryError, very soon if tested without XNIO-345 fix

      Show
      Configure -XX:MaxDirectMemorySize=16M for server to hit error earlier . E.g. add into JAVA_OPTS of standalone.conf run server Run this reproducer loop.sh #!/bin/bash for i in {1..10000} do echo $i ${jboss.home}/bin/jboss-cli.sh -c ":reload" if [ $? == 1 ] then break fi done Eventually you will get an OutOfMemoryError, very soon if tested without XNIO-345 fix

    Description

      ByteBufferSlicePool is used at two points in the server:

      • BufferPoolService (io subsystem)
      • ManagementHttpServer (domain http server)

      This pool should:

      • whenever possible be static, i.e., be not recreated at every reloaded
      • when not possible, we must use the clean() method added via XNIO-317 and fixed by XNIO-346

      Attachments

        Issue Links

          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4601 Upgrade XNIO to 3.7.3.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17380 (7.2.z) WFCORE-4600 - Memory leak caused by ByteBufferSlicePool usage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) UNDERTOW-1277 Clear XnioByteBufferPool.PooledByteBuffer pool when close() to avoid direct memory leaking

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              flaviarnn Flavia Rainone
              flaviarnn Flavia Rainone
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: