Re: [jelly] Maven JSL memory leak and Jelly

2005-01-29 Thread Brett Porter
:36 AM To: Jakarta Commons Developers List Subject: Re: [jelly] Maven JSL memory leak and Jelly The good news: nailed it in xdoc. If you run multiproject:goal -Dgoal=xdoc, you only need about 13mb of memory for any number of projects. Tha bad news: multiproject:goal -Dgoal=site still leaks

Re: [jelly] Maven JSL memory leak and Jelly

2005-01-27 Thread Brett Porter
be fixed now. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 10:09 PM To: Jakarta Commons Developers List Subject: RE: [jelly] Maven JSL memory leak and Jelly Thanks Hans! That's what I was thinking of doing, so I'm glad you've got it under control

Re: [jelly] Maven JSL memory leak and Jelly

2005-01-27 Thread Dion Gillard
To: Jakarta Commons Developers List Subject: RE: [jelly] Maven JSL memory leak and Jelly Thanks Hans! That's what I was thinking of doing, so I'm glad you've got it under control. When I was testing, the size of the included JSL affected the amount of memory leaked, so I guess it is tag

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-27 Thread Hans Gilde
Commons Developers List Subject: Re: [jelly] Maven JSL memory leak and Jelly The HtmlUnit jelly tests pass as well with CVS HEAD. No mysterious GC errors. On Thu, 27 Jan 2005 22:36:28 +1100, Brett Porter [EMAIL PROTECTED] wrote: The good news: nailed it in xdoc. If you run multiproject:goal

Re: [jelly] Maven JSL memory leak and Jelly

2005-01-27 Thread Hans Gilde
. -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Thursday, January 27, 2005 7:50 PM To: Jakarta Commons Developers List Subject: Re: [jelly] Maven JSL memory leak and Jelly The HtmlUnit jelly tests pass as well with CVS HEAD. No mysterious GC errors. On Thu, 27

Re: [jelly] Maven JSL memory leak and Jelly

2005-01-27 Thread Dion Gillard
and screwed it up. I'm going to commit the changes with come added comments. -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Thursday, January 27, 2005 7:50 PM To: Jakarta Commons Developers List Subject: Re: [jelly] Maven JSL memory leak and Jelly

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-27 Thread Hans Gilde
issue, it should be fixed now. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 10:09 PM To: Jakarta Commons Developers List Subject: RE: [jelly] Maven JSL memory leak and Jelly Thanks Hans! That's what I was thinking of doing, so I'm glad

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-26 Thread Hans Gilde
It was just a little issue, it should be fixed now. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 10:09 PM To: Jakarta Commons Developers List Subject: RE: [jelly] Maven JSL memory leak and Jelly Thanks Hans! That's what I was thinking

[jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Brett Porter
Hi, I did some testing and can confirm that the current site generation memory leak occurs here: j:file name=${outFile} encoding=${outputencoding} omitXmlDeclaration=true outputMode=xml prettyPrint=no -- j:include uri=${stylesheet.toString()}/ /j:file If

Re: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Paul Libbrecht
Ideally, a test-case would be awesome, even if it refers to some far-away stylesheet... Can you try calling .clear() on the result of this context.runScript(uri, output, isExport(), isInherit()) (and the other call). Maybe that'll help. In all cases, this context is gc-ed

Re: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Brett Porter
Paul Libbrecht wrote: Ideally, a test-case would be awesome, even if it refers to some far-away stylesheet... I'll try and narrow it down first by cutting down site.jsl to the minimum that leaks. Can you try calling .clear() on the result of this context.runScript(uri, output,

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Hans Gilde
Why won't RC2 work with maven 1.0.x? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 7:30 AM To: Jakarta Commons Developers List Subject: Re: [jelly] Maven JSL memory leak and Jelly Paul Libbrecht wrote: Ideally, a test-case would

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Brett Porter
, 2005 7:30 AM To: Jakarta Commons Developers List Subject: Re: [jelly] Maven JSL memory leak and Jelly Paul Libbrecht wrote: Ideally, a test-case would be awesome, even if it refers to some far-away stylesheet... I'll try and narrow it down first by cutting down site.jsl

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Hans Gilde
There's definitely a leak in the include tag. Brett, I'm guessing that this leak also exists pre-RC2, right? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 7:30 AM To: Jakarta Commons Developers List Subject: Re: [jelly] Maven JSL memory

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Brett Porter
guessing that this leak also exists pre-RC2, right? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 7:30 AM To: Jakarta Commons Developers List Subject: Re: [jelly] Maven JSL memory leak and Jelly Paul Libbrecht wrote: Ideally, a test

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Hans Gilde
: Monday, January 24, 2005 9:47 PM To: Jakarta Commons Developers List Subject: RE: [jelly] Maven JSL memory leak and Jelly Yup. AFAICT, it's been there since it's creation. Do you need some additional info from me? I'm happy to try to make a smaller test case and/or test with Maven later

RE: [jelly] Maven JSL memory leak and Jelly

2005-01-24 Thread Brett Porter
the only one leaking. Once we fix this problem, a retest will definitely be in order. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 24, 2005 9:47 PM To: Jakarta Commons Developers List Subject: RE: [jelly] Maven JSL memory leak and Jelly Yup