Andreas, sorry for not responding for so long, but I have been busy with a lot of other stuff.
Andreas Andreou wrote: > Chrome's Developer Tools (ctrl+shift+i) have a "profiles" tab. > Once selected, you'll find a "Take heap snapshot" at the bottom... > press it once at the start, then again at the end of the activity > you want to perform and it'll show you what changed Thanks a lot for the hint. I have tried the developer tools but only came to the conclusion that something is leaking memory, which didn't get me very far. I also spent some days with trying tapestry 5.2, hacking tapestry.js, trying to rephrase bits of code that looked suspicious to me, but without much success. Today I also tried the new prototype RC, but the results were comparable to the 1.6.1 one. Today I stumbled upon a ticket in the prototype bugtracker [1], and after applying parts of the appended patch and playing around, I am now sure, that it is definitely related. Unfortunately, that patch increases the CPU usage considerably, mostly due to the CACHE=CACHE.without(element) line. I haven't yet made up my mind whether to completely remove the CACHE parts (which seem to be needed for IE only, which I don't care about for that project) or spend more time to find a better way, but I thought I'd share my findings. Regards, Jochen [1] https://prototype.lighthouseapp.com/projects/8886/tickets/466 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
