On Oct 18, 2009, at 7:34 PM, Caleb James DeLisle wrote:
> Hi,
> I have experienced the same problem.
> I noticed that the memory used by java does not exceed 200Mb even if
> Xmx is 2048m.
> Also it seems that a separate java process is spawned to do the tests.
>
> Found this:
> [nbdev] Re: Increased heap size does not apply to junit tests ...
> http://markmail.org/message/2s6ejry3h46lijry
>
> I updated to revision 24348 (from 10/09/2009) which I think built
> okay before, but I still got the error.
>
> I suspect a changed dependency just pushed it over the default 128m
> limit.
Indeed increasing the memory makes it work:
<argLine>-Xms256m -Xmx512m</argLine>
However it's symptomatic of a problem: it means we have a memory leak
in our tests. We need to fix it rather than increase the memory.
-Vincent
> Caleb James DeLisle
>
> Vincent Massol wrote:
>> On Oct 18, 2009, at 9:29 AM, Vincent Massol wrote:
>>
>>> Hi,
>>>
>>> Today I just got my first OOM when building xwiki. It happened in
>>> the xwiki-core tests:
>>>
>>> Running com.xpn.xwiki.notify.PropertyChangedRuleTest
>>> org.apache.maven.surefire.booter.SurefireExecutionException: Java
>>> heap space; nested exception is java.lang.OutOfMemoryError: Java
>>> heap space
>>> java.lang.OutOfMemoryError: Java heap space
>>>
>>> The bad part is that I'm building with:
>>> MAVEN_OPTS=-Xmx1024m
>>>
>>> Anyone else has noticed a memory req increase in the build?
>>
>> The build stops on the PropertyChangedRuleTest so I believe there's a
>> problem in the code somewhere that leads to the OOM.
>>
>> -Vincent
>>
>>> Thanks
>>> -Vincent
>>
>> _______________________________________________
>> devs mailing list
>> [email protected]
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
