[ 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-deprioritized-minor auto-unassigned pull-request-available (was: auto-deprioritized-critical auto-deprioritized-major auto-unassigned pull-request-available stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, 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: Not a Priority > Labels: auto-deprioritized-critical, auto-deprioritized-major, > auto-deprioritized-minor, 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.20.1#820001)