On Mon, 04 Jul 2011 08:20:01 -0300, Taha Hafeez
wrote:
Hi Thiago
Hi!
I learned it the very hard way but am not sure why this happens
I guess this happens because the Zone JavaScript logic is executed once
when the page is rendered. When the Zone is updated, if you return the
whole Z
On Mon, 04 Jul 2011 00:36:01 -0300, Taha Hafeez
wrote:
Hi
Hi!
Finally I disabled the timer and used fast manual clicks to check if the
problem was with the zone itself. What I found was that if I return
zone.getBody() then there is no memory leak but if I return zone then
there is a con
Hi,
Afaik, zone div contents is replaced by whatever server side returns
from event handler method.
That is, if you return a zone Tapestry will faithfully replace zone
contents with a copy of original zone...
after all, you could return a completely different zone than the
original one.
Ref
Hi
I just opened the task manager to see the usage to iexplorer process and it
starts increasing by 3 - 80k for each refresh based on the size of the page
In chrome, firefox & opera everything seems ok
regards
Taha
On Mon, Jul 4, 2011 at 10:13 AM, Josh Canfield wrote:
> What do you use for me
What do you use for memory profiling in IE?
On Jul 3, 2011 8:36 PM, "Taha Hafeez" wrote:
> Hi
>
> While working on the Zone-refresh component, I was testing it on IE8 and
> found that it resulted in memory leak... After working on it the whole day
I
> couldn't get around it.
>
> Finally I disabled
Hi
While working on the Zone-refresh component, I was testing it on IE8 and
found that it resulted in memory leak... After working on it the whole day I
couldn't get around it.
Finally I disabled the timer and used fast manual clicks to check if the
problem was with the zone itself. What I found
