[
https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21799:
-----------------------------------
Labels: stale-assigned (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it. If the "warning_label" label is not removed in 7 days, the
issue will be automatically unassigned.
> Detect and fail explicitly on managed memory leaking
> ----------------------------------------------------
>
> Key: FLINK-21799
> URL: https://issues.apache.org/jira/browse/FLINK-21799
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Major
> Labels: stale-assigned
> Fix For: 1.14.0
>
>
> As discussed in FLINK-21419, it would be helpful to fail explicitly if a
> managed memory leaking is detected.
> The leaking can be detected as:
> * A segment being GC-ed is never freed.
> * A memory manager being closed does not have all its memory released.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
