[
https://issues.apache.org/jira/browse/LUCENE-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466469#comment-13466469
]
Dawid Weiss commented on LUCENE-4451:
-------------------------------------
This is a border case. The problem is most likely not the threads themselves
but also the fact that they keep refs to some other data structures (in thread
locals)? I'll see what I can do not to keep hard refs to those thread/context
pairs though. I remember there was a reason I didn't use soft refs for this
from the beginning but I can't tell you right now what it was.
> Memory leak per unique thread caused by RandomizedContext.contexts static map
> -----------------------------------------------------------------------------
>
> Key: LUCENE-4451
> URL: https://issues.apache.org/jira/browse/LUCENE-4451
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Dawid Weiss
>
> In digging on the hard-to-understand OOMEs with
> TestDirectPostingsFormat ... I found (thank you YourKit) that
> RandomizedContext (in randomizedtesting JAR) seems to be holding onto
> all threads created by the test. The test does create many very short
> lived threads (testing the thread safety of the postings format), in
> BasePostingsFormatTestCase.testTerms), and somehow these seem to tie
> up a lot (~100 MB) of RAM in RandomizedContext.contexts static map.
> For now I've disabled all thread testing (committed {{false &&}} inside
> {{BPFTC.testTerms}}), but hopefully we can fix the root cause here, eg
> when a thread exits can we clear it from that map?
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
