[
https://issues.apache.org/jira/browse/DRILL-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781744#comment-15781744
]
Paul Rogers commented on DRILL-5160:
------------------------------------
Also seeing a similar problem in {{FragmentContext.close()}} in the unit test
{{TestConvertFunctions#testConvertFromConvertToInt}}. This test fails with the
Snappy library issue. Then, when tearing down, we get an
{{IllegalStateException}} in the {{OperatorContextImpl.close()}} method here:
{code}
if (allocator != null) {
allocator.close(); // Error here
}
{code}
Likely, again, the thread is not being closed properly before the memory
allocator is released.
> Memory leak in Parquet async reader when Snappy fails
> -----------------------------------------------------
>
> Key: DRILL-5160
> URL: https://issues.apache.org/jira/browse/DRILL-5160
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.9.0
> Reporter: Paul Rogers
> Assignee: Parth Chandra
>
> See the details in DRILL-5157. The Parquet async reader uses the Snappy
> library. If the call into Snappy fails (in my case, due to missing dependency
> management in the Drill pom.xml file), the Parquet reader fails (as it
> should.)
> Unfortunately, the Parquet reader leaks memory which cause
> {{IllegalStateException}} errors in production, assertion failures in unit
> tests.
> To reproduce this the easy way (to avoid the need to undo the fix for
> DRILL-5157 in Snappy dependencies), use Drill's exception injector in inject
> an exception at the line where we call into Snappy (See DRILL-5157 for
> details.)
> Set a breakpoint exception for {{IllegalStateException}} you will see the
> memory leak.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
