[
https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21799:
-----------------------------------
Labels: auto-deprioritized-major (was: stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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 / Coordination
> Reporter: Xintong Song
> Priority: Minor
> Labels: auto-deprioritized-major
> 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)
