lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4252) Detect/Fail tests when they leak RAM in static fields
Date Tue, 31 Jul 2012 07:48:36 GMT


Dawid Weiss updated LUCENE-4252:

    Attachment: sfi.patch

This is useful in general. I've added this to randomized testing package, modifying Robert's
code slightly to:

- exclude static final fields (typically constants that cannot be erased);
- exclude fields of primitive types
- include sorted RAM usage info for accounted fields in the assertion thrown.

Exclusion rules are customizable via rule subclassing (accept(Field) method).
> Detect/Fail tests when they leak RAM in static fields
> -----------------------------------------------------
>                 Key: LUCENE-4252
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Test
>          Components: general/test
>            Reporter: Robert Muir
>            Assignee: Dawid Weiss
>         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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message