RFS: java3d 1.5.2+dfsg-3

On Fri, 21 Aug 2009 16:01:11 +0200, Torsten Werner <twerner RemoveThis @debian.org>
wrote:
> On Mon, Aug 17, 2009 at 2:39 PM, Onkar Shinde<onkarshinde RemoveThis @gmail.com>
wrote:
>> I am looking for the sponsorship of new revision of java3d.
>
> It builds on sparc, ia64, and amd64 but I see strange messages during
> javadoc. The build log
> <http://people.debian.org/~twerner/java3d_1.5.2+dfsg-3_amd64.build.gz>.
> Does anyone have an idea what might be wrong?

java.lang.OutOfMemoryError: GC overhead limit exceeded

>From [1] :
"
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.
"

GC seems to spend too much time trying to free heap memory.
You should try :
#1 to fork=yes Javadoc ant task
+
#2 to pass -Xmx parameter to javadoc cmd

If this doesn't work try to set -XX:-UseGCOverheadLimit.

[1]
http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html#par_gc.oom

--
Damien Raude-Morvan - http://damien.raude-morvan.com/


--
To UNSUBSCRIBE, email to debian-java-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org

On Fri, Aug 21, 2009 at 4:59 PM, Damien
Raude-Morvan<damien DeleteThis @raude-morvan.com> wrote:
> 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.

Torsten


--
To UNSUBSCRIBE, email to debian-java-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org

On Fri, Aug 21, 2009 at 11:19 PM, Damien
Raude-Morvan<drazzib RemoveThis @drazzib.com> wrote:
> 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

Horror! Upstream's build.xml sets the maxmemory attribute to 128m and
I am building on a 64 bit arch. It builds fine after removing the
attribute. I have uploaded the package now.

Cheers,
Torsten


--
To UNSUBSCRIBE, email to debian-java-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org