Uploaded image for project: 'XNIO'
  1. XNIO
  2. XNIO-345

ByteBufferSlicePool instances are not garbage collected

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.7.2.Final
    • Fix Version/s: 3.7.3.Final
    • Component/s: api
    • Labels:
      None
    • Steps to Reproduce:
      Hide
      • Configure -XX:MaxDirectMemorySize=16M for WildFly to hit error earlier . E.g. add into JAVA_OPTS of standalone.conf
      • run WildFly
      • Run this reproducer
        loop.sh
        #!/bin/bash
        for i in {1..100}
        do
          echo $i
          ${jboss.home}/bin/jboss-cli.sh -c ":reload"
          if [ $? == 1 ]
          then
              break
          fi
        done
        
      Show
      Configure -XX:MaxDirectMemorySize=16M for WildFly to hit error earlier . E.g. add into JAVA_OPTS of standalone.conf run WildFly Run this reproducer loop.sh #!/bin/bash for i in {1..100} do echo $i ${jboss.home}/bin/jboss-cli.sh -c ":reload" if [ $? == 1 ] then break fi done

      Description

      This bug can be verified by reloading the WildFly server several times.

      This pool is never garbage collected. The leak is caused by the ThreadLocal<ThreadLocalCache> variable.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  flavia.rainone Flavia Rainone
                  Reporter:
                  flavia.rainone Flavia Rainone
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: