You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Commit Tag Bot (JIRA)" <ji...@apache.org> on 2013/03/22 17:43:16 UTC
[jira] [Commented] (LUCENE-4252) Detect/Fail tests when they leak
RAM in static fields
[ https://issues.apache.org/jira/browse/LUCENE-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610872#comment-13610872 ]
Commit Tag Bot commented on LUCENE-4252:
----------------------------------------
[branch_4x commit] Dawid Weiss
http://svn.apache.org/viewvc?view=revision&revision=1383842
LUCENE-4252: Detect/Fail tests when they leak RAM in static fields.
> Detect/Fail tests when they leak RAM in static fields
> -----------------------------------------------------
>
> Key: LUCENE-4252
> URL: https://issues.apache.org/jira/browse/LUCENE-4252
> Project: Lucene - Core
> Issue Type: Test
> Components: general/test
> Reporter: Robert Muir
> Assignee: Dawid Weiss
> Fix For: 4.0, 5.0
>
> Attachments: LUCENE-4252.patch, LUCENE-4252.patch, sfi.patch
>
>
> We run our junit tests without firing up a JVM each time.
> But some tests initialize lots of stuff in @BeforeClass and don't properly null it out in an @AfterClass, which can cause a subsequent test in the same JVM to OOM, which is difficult to debug.
> Inspiration for this was me committing Mike's cool TestPostingsFormat, which forgot to do this: then we were seeing OOMs in several jenkins runs.
> We should try to detect these leaks in LuceneTestCase with RAMUsageEstimator and fail the test.
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org