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

ByteBufferSlicePool FREE_DIRECT_BUFFERS is always empty

    Details

      Description

      This issue is a regression caused by XNIO-358, reintroducing the original bug represented by XNIO-346.
      The PR must be reverted, the reason all memory directly allocated should be added to directBuffers is so that we can add (or readd) the "freed" direct memory on clean. If we never add the buffers to directBuffers, it will always be empty, and so FREE_DIRECT_BUFFERS is not populated on clean.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: