[
https://issues.apache.org/jira/browse/FLINK-12189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12189:
-----------------------------------
Labels: auto-deprioritized-critical auto-unassigned
pull-request-available (was: auto-unassigned pull-request-available
stale-critical)
Priority: Major (was: Critical)
This issue was labeled "stale-critical" 7 ago and has not received any updates
so it is being deprioritized. If this ticket is actually Critical, please raise
the priority and ask a committer to assign you the issue or revive the public
discussion.
> Fix bugs and typos in memory management related code
> ----------------------------------------------------
>
> Key: FLINK-12189
> URL: https://issues.apache.org/jira/browse/FLINK-12189
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Reporter: Liya Fan
> Priority: Major
> Labels: auto-deprioritized-critical, auto-unassigned,
> pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are some bugs and typos in the memory related source code. For example,
> # In MemoryManager.release method, it should throw an NPE, if the input is
> null. But it does not.
> # In HybridMemorySegment.put and get methods, the number of bytes
> read/written should be specified by the input parameter, rather than
> reading/writing until the end.
> # In HeapMemorySegment, the data member memory should be returned. This is
> because the member heapArray will not be reset to null after calling the
> release method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
