Hi Torsten, > > The concurrent collector will throw an OutOfMemoryError if too much time > > is being spent in garbage collection: if more than 98% of the total time > > is spent in garbage collection and less than 2% of the heap is recovered, > > an OutOfMemoryError will be thrown. This feature is designed to prevent > > applications from running for an extended period of time while making > > little or no progress because the heap is too small. If necessary, this > > feature can be disabled by adding the option -XX:-UseGCOverheadLimit to > > the command line. > > The difference between 1.5.2+dfsg-3 and 1.5.2+dfsg-2 are two > portability patches that are not related to javadoc at all but javadoc > fails for 1.5.2+dfsg-3 and not for 1.5.2+dfsg-2. On my amd64, I'm getting "GC overhead limit exceeded" with 1.5.2+dfsg-*2* but I've managed to get 1.5.2+dfsg-*3* successfuly built :) To my understanding, it might probably be linked to some GC memory limit: Javadoc generation seems always getting near Xmx128m limit (default) and, under some conditions, (others process, CPU avaible time for garbage collector ?) it might exceeds this 98% mark and throw an OOM. Cheers, -- Damien Raude-Morvan - http://damien.raude-morvan.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.