[
https://issues.apache.org/jira/browse/FLINK-21798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303080#comment-17303080
]
Kezhu Wang commented on FLINK-21798:
------------------------------------
[~xintongsong] You are right. It is always a good to catch multiple-frees.
There are already places in {{MemorySegment}} forbidding "access after freed",
no excuse to leave multiple-frees behind.
> Guard MemorySegment against multiple frees.
> -------------------------------------------
>
> Key: FLINK-21798
> URL: https://issues.apache.org/jira/browse/FLINK-21798
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Xintong Song
> Priority: Critical
> Labels: Umbrella
> Fix For: 1.13.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
