Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.2.0, 1.1.4, 1.3.0, 1.1.5, 1.2.1, 1.2.2, 1.3.1, 1.4.0, 1.3.2, 1.3.3
    • Fix Version/s: 1.5.0, 1.4.1
    • Component/s: Network
    • Labels:
      None

      Description

      SpillableSubpartitionView#releaseMemory() recycles its buffers twice: once asynchronously after the write operation and once in SpillableSubpartitionView#releaseMemory() after adding the write operation to the queue.

      1) if SpillableSubpartitionView#releaseMemory() hits first and the buffer is recycled, the memory region may already be reused despite the pending write
      2) If, for some reason (probably only in tests like SpillableSubpartitionTest#testConsumeSpillablePartitionSpilledDuringConsume()?), the buffer is retained and to be used in parallel somewhere else it may also not be available anymore or contain corrupt data.

        Attachments

          Activity

            People

            • Assignee:
              NicoK Nico Kruber
              Reporter:
              NicoK Nico Kruber
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: