I slurped this hprof down and opened it w/ YourKit... Something weird is going on, because there is a single massive (151 MB) string, stack local to one of the threads, filled with character U+00B2.
The test itself looks innocuous; I don't think it creates any massive stack local strings. I'm baffled. Robert maybe something crazy is happening in RuleBasedCollator? Mike http://blog.mikemccandless.com On Mon, May 2, 2011 at 5:53 AM, Apache Jenkins Server <[email protected]> wrote: > Build: https://builds.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/7642/ > > 1 tests failed. > REGRESSION: > org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe > > Error Message: > Java heap space > > Stack Trace: > java.lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2894) > at > java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:117) > at > java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:589) > at java.lang.StringBuffer.append(StringBuffer.java:337) > at > java.text.RuleBasedCollator.getCollationKey(RuleBasedCollator.java:617) > at > org.apache.lucene.collation.CollationKeyFilter.incrementToken(CollationKeyFilter.java:93) > at > org.apache.lucene.collation.CollationTestBase.assertThreadSafe(CollationTestBase.java:304) > at > org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe(TestCollationKeyAnalyzer.java:89) > at > org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1091) > at > org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(LuceneTestCase.java:1023) > > > > > Build Log (for compile errors): > [...truncated 9253 lines...] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
