(bf) Concurrency issue in DirectByteBuffer.Deallocator

XMLWordPrintable

    • b15

        The DirectByteBuffer.Deallocator is run via a Cleaner which, in turn, is run in a separate thread. This means the deallocator must be thread-safe. However, this is not the case as it does not adhere to fundamental safe-publication rules and modifies its internal state with normal memory semantics.

              Assignee:
              Per-Ake Minborg
              Reporter:
              Per-Ake Minborg
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: