You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:05 UTC

[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking

     [ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yun Gao updated FLINK-21799:
----------------------------
    Fix Version/s: 1.16.0

> 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.15.0, 1.16.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.20.1#820001)