Details
-
Sub-task
-
Status: Closed
-
Critical
-
Resolution: Done
-
None
Description
This ticket tracks the effort that:
Guard memory segment against multiple frees, ensuring the underlying memory is only released once.
Introduce a configuration option to explicitly fail on multiple-frees, which helps detects the cases.
Attachments
Issue Links
- is blocked by
-
FLINK-21236 Don't explicitly use HeapMemorySegment in raw format serde
-
- Closed
-
- links to