[
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-deprioritized-major
auto-unassigned pull-request-available stale-minor (was:
auto-deprioritized-critical auto-deprioritized-major auto-unassigned
pull-request-available)
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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-unassigned, pull-request-available, stale-minor
> 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.20.1#820001)
