Re: [Jelly] Memory leak revealed

Hans Gilde wrote: Paul, this looks just like the leak that's been fixed. It's all the stuff getting stuck in the ThreadLocal. Augustin, have you tried this with the latest build of Jelly? Hans Hans No, it isn´t the ThreadLocal thing, that was another problem I got fixed as a patch to beta4

Re: [Jelly] Memory leak revealed

Le 23 mars 05, à 06:04, Brett Porter a écrit : The additional patch caused a fairly large breakage in Maven indicating it was not backwards compatible. Paul was still investigating when he had time, last I heard. Sadly, I did not have the cycles to finalize that... and will be offline for 10

Re: [Jelly] Memory leak revealed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Libbrecht wrote: Le 23 mars 05, à 06:04, Brett Porter a écrit : The additional patch caused a fairly large breakage in Maven indicating it was not backwards compatible. Paul was still investigating when he had time, last I heard. Sadly, I

Re: [Jelly] Memory leak revealed

Hans, I remember the time you posted this patch, you were positively enthusiastic and sure but did not give much comments as to why it was leaking and why this avoided it. Maybe you could make it more precise ? thank you paul Le 23 mars 05, à 23:54, Brett Porter a écrit : I'm probably a month

RE: [Jelly] Memory leak revealed

This is one of the bugs that's been fixed by the last memory patch. -Original Message- From: Agustin Ramos [mailto:[EMAIL PROTECTED] Sent: Friday, March 18, 2005 10:54 PM To: Jakarta Commons Developers List Subject: [Jelly] Memory leak revealed I've been struggling to find a memory leak

RE: [Jelly] Memory leak revealed

To: Jakarta Commons Developers List Subject: Re: [Jelly] Memory leak revealed Agustin, I've been trying to reproduce your error, which may be believable I fear. I tried to make it simpler, as you described, ... and I did not manage it... Also, you seem to be running a code that calls jelly

Re: [Jelly] Memory leak revealed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hans, Are you referring to current SVN, or current SVN with your additional patch (that has not yet been committed) applied? The additional patch caused a fairly large breakage in Maven indicating it was not backwards compatible. Paul was still

Re: [Jelly] Memory leak revealed

Agustin, I've been trying to reproduce your error, which may be believable I fear. I tried to make it simpler, as you described, ... and I did not manage it... Also, you seem to be running a code that calls jelly that calls the code again which seems much compared to what you describe. The

[Jelly] Memory leak revealed

I've been struggling to find a memory leak in an enterprise app whose GUI we developed using jelly-swing. Finally I've been able to make a minimalistic test which demonstrates the leak. The problem is with the define:taglib and define:tag tags. The test shows how repeteadly invoking a tag

Re: [Jelly] memory leak

Aha, Scott Howlett pointed us to an existing bug that descibes this issue and includes a patch! It looks good to me, so I'm applying it now. - Morgan --- Morgan Delagrange [EMAIL PROTECTED] wrote: Hey all, We recently discovered a pretty serious memory inefficiency in Jelly. Although it's