[
https://issues.apache.org/jira/browse/HIVE-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775832#comment-13775832
]
Hive QA commented on HIVE-5345:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12604653/HIVE-5345.01.patch
{color:green}SUCCESS:{color} +1 3143 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/858/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/858/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> Operator::close() leaks Operator::out, holding reference to buffers
> -------------------------------------------------------------------
>
> Key: HIVE-5345
> URL: https://issues.apache.org/jira/browse/HIVE-5345
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.13.0
> Environment: Ubuntu, LXC, jdk6-x86_64
> Reporter: Gopal V
> Assignee: Gopal V
> Labels: memory-leak
> Attachments: HIVE-5345.01.patch, out-leak.png
>
>
> When processing multiple splits on the same operator pipeline, the output
> collector in Operator has a held reference, which causes issues.
> Operator::close() does not de-reference the OutputCollector object
> Operator::out held by the object.
> This means that trying to allocate space for a new OutputCollector causes an
> OOM because the old one is still reachable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
