OK, now I got the OOME as well with my local in-memory H2 changes.

it failed in ObservationRefreshTest. I analyzed the heap dump and
it looks like the memory usage of this particular test is quite high
because it uses orderable child nodes and adds child nodes one
by one.

I think that can be easily changed...

Regards
 Marcel

> -----Original Message-----
> From: Julian Reschke [mailto:julian.resc...@gmx.de]
> Sent: Mittwoch, 26. März 2014 21:23
> To: oak-dev@jackrabbit.apache.org
> Subject: Re: svn commit: r1581376 - /jackrabbit/oak/trunk/oak-
> jcr/src/test/java/org/apache/jackrabbit/oak/jcr/NodeStoreFixture.java
> 
> On 2014-03-26 21:08, Marcel Reutegger wrote:
> > Hi,
> >
> > locally, I reverted your change and the build runs fine for me.
> > that's why I thought it might work for you as well if we increase
> > the heap slightly.
> >
> > or does it only happen when you run the build with some specific
> > profile?
> > ...
> 
> No, it was failing for me with the default profile.
> 
> Best regards, Julian

Reply via email to