Dear Daniel,
I noticed a similar problem with UlcTree, not a memory leak but a high memory
consumption on client side (in my case creating an OutOfMemoryError). Your test
case will not reveal this as you take memory snapshots before and after
running. I opened all tree nodes in a tree with 1000 entries having 1 or more
children. The rendering on client side too about 4 minutes and needed more that
90 MB memory on client side while doing so.
Best Regards,
Ilja Pavkovic
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Daniel Grob
Sent: Tuesday, September 25, 2007 10:55 AM
To: [email protected]; M Asif
Subject: Re: [ULC-developer] FW: ULCTree memory leak -
Hi Asif,
I could not reproduce the behavior you describe. Here is what I did:
* I started the ULCSet sample with help of the ULCSetDevelopmentLauncher class
* I selected the TableTree tab in the main window
* I opened the "System III" node in the table tree
* I took a memory snapshot with a profiler
* I closed / opened the "System III" node for several times
* I took another memory snapshot with a profiler
* I compared the two memory snapshots
The comparison of the two memory snapshots showed no irregularities.
Could you please tell us how you identified the memory leak? Thanx!
Regards Dany
On 26.09.2007, at 07:33, Janak Mulani wrote:
-----Original Message-----
From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] Behalf Of M Asif
Sent: Tuesday, September 25, 2007 2:57 AM
To: [EMAIL PROTECTED]
Subject: ULCTree memory leak -
ULC version 6.1.3
Hi,
Expanding and collapsing same tree node keep on increasing client JVM memory
usage. I have even noticed the same behavior in your demo (
http://www.canoo.com/ulc/demos/wfbrowser.html) for tabltree component. Its look
very critical issue. is there any workaround? thanks in advance.
Kind Regards,
-Asif
_____
Gear up for Halo® 3 and get a $25 Best Buy gift card. It’s our way of saying
thanks for using Windows Live™. Get it
<http://gethalo3gear.com?ocid=SeptemberWLHalo3_WLHMTxt_1> now!
