[
https://issues.apache.org/jira/browse/FLINK-21419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299989#comment-17299989
]
Kezhu Wang commented on FLINK-21419:
------------------------------------
Coming from FLINK-21728, given the severity of native memory
issues(double/missing free), I would suggest following:
* Always protect double-freeing in freeing code. Throws exception if possible
in double free.
* Bump up freeing to where allocation happens. This means returning explicit
typed native memory {{OwnedNativeMemory}} from {{MemoryUtils.allocateUnsafe}} .
* Always keep gc cleaner as fallback to diagnose leaking issue.
cc [~dwysakowicz] [~xintongsong] [~trohrmann] [~ykt836] [~nicholasjiang]
> Remove GC cleaner mechanism for unsafe memory segments
> ------------------------------------------------------
>
> Key: FLINK-21419
> URL: https://issues.apache.org/jira/browse/FLINK-21419
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Xintong Song
> Assignee: Nicholas Jiang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
