[FLINK-21798] Guard MemorySegment against multiple frees.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: 1.14.0
• Component/s: Runtime / Coordination
• Labels: Umbrella pull-request-available
• Assignee: Xintong Song
• Reporter: Xintong Song
• Created: 15/Mar/21 10:44
• Updated: 27/Feb/23 12:58
• Resolved: 19/Apr/21 07:14

Description

As discussed in FLINK-21419, freeing a memory segment for multiple times usually indicates the ownership of the segment is unclear. It would be good to gradually getting rid of all such multiple-frees.

This ticket serves as an umbrella for detected multiple-free cases.

Issue Links

• causes: FLINK-31244 OffHeapUnsafeMemorySegmentTest.testCallCleanerOnceOnConcurrentFree prints IllegalStateException
• links to: GitHub Pull Request #15566

Sub-Tasks

• Guard MemorySegment against concurrent frees.: Closed
• DegreesWithExceptionITCase crash: Closed
• DemultiplexingRecordDeserializerTest fail due to multiple memory freeing: Closed