forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam R. B. Jack" <aj...@trysybase.com>
Subject Fw: Hermes Run (was Re: Missing Documentation)
Date Tue, 04 May 2004 21:29:15 GMT
Folks,

I don't know how aware you are (if at all) the Python Gump uses Forrest to
convert xdocs (and SVGs) that represent it's run, into a site. This link is
on one site, and references others:

    http://lsd.student.utwente.nl/gump/servers.html

The Python code generates the XML, then launches forrest (pretty recent
versions) against that.

Unfortunately there are times when forrest just goes wacky, it's memory
usage grows unbelievably & it bogs down to a crawl. I'm not sure if this is
an obvious leak, or some sort of garbage collector confusion, or what.
Unfortunately it isn't easily reproducible (although it might be on
hermes.apache.org right now). I think it comes when given a certain number
of artefacts to produce (where that number is quite large, few thousand.)

Does anybody have any thoughts on Forrest tuning, or tracing, or whatever to
attempt to dig into and/or resolve this problem?

Thanks in advance.

regards,

Adam
----- Original Message ----- 
From: "Adam R. B. Jack" <ajack@trysybase.com>
To: <general@gump.apache.org>
Sent: Tuesday, May 04, 2004 2:54 PM
Subject: Re: Hermes Run (was Re: Missing Documentation)


> > > Many of the generated files on hermes are missing after the 2004-05-03
> > > run.  Nothing for commons-net seems present, "Projects Issues",
> > > "Projects Fixes" are missing, "Modules All" and so on.  No system I
> > > could identify.
>
> Ok, got it -- or the symptom, if not the cause. The forrest run grows
> obscenely, I swear I saw something like 1200M. Anyway after an hour of
> plodding along, slowely generating pages, Gumpy gives up waiting. It kills
> the shell, but not the forrest (to no problems to be seen in forrest.txt).
> Gumpy then copies the documents it has to the current point, i.e. not all.
>
> I'd like to know why Forrest is growing so huge, but I doubt I am the man
to
> debug it. I wonder if it is to do with the little SVGs I added, I might
> remove them. [I've kept the big SVGs to my box only.]
>
> Anyways -- either we get rid of forrest as batch, and/or I trim docs/SVGs,
> and/or I change the output to be raw HTML & get on with my life...
>
> regards
>
> Adam
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>


Mime
View raw message