[
https://issues.apache.org/jira/browse/CASSANDRA-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297861#comment-15297861
]
Robert Stupp commented on CASSANDRA-11867:
------------------------------------------
Thanks!
Committed as ffd10a9b9a391f6bb55daa7e9365bff34f945f73 to 2.2, as
361c4e4c7000bcfded4ea81f6ebd59eeed42ab31 to 3.0 and merged to 3.7 and trunk.
Yes, accessing a closed stream is never a good idea. But better to error out
fast instead of leaving it in a weird state.
> Possible memory leak in NIODataInputStream
> ------------------------------------------
>
> Key: CASSANDRA-11867
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11867
> Project: Cassandra
> Issue Type: Bug
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Fix For: 2.2.6, 3.7, 3.0.7, 3.8
>
>
> {{NIODataInputStream}} allocates direct memory but does not clean it on
> close. Proposed patch adds a call to {{FileUtils.clean()}} for this direct
> memory buffer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
