[
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-major (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 issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: stale-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)
