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

ByteBufferSlicePool FREE_DIRECT_BUFFERS is always empty

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.7.8.Final, 3.8.1.Final
    • None
    • None
    • None

    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.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19542 (7.3.z) XNIO-374 - ByteBufferSlicePool FREE_DIRECT_BUFFERS is always empty

          • 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 incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19543 (7.2.z) XNIO-374 - ByteBufferSlicePool FREE_DIRECT_BUFFERS is always empty

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: