Hi, I am currently writing a webapp with tapestry 5 and have come to a point where I want a zone to be updated regularly. That works quite well using just a small amount of custom JavaScript. However, I noticed that the browser's memory seems to fill up over the time. The application updates two zones with multiple grids, some of them again wrapping their cell content in event links that can be used to filter the grid. The zones are updated every 15 seconds. When leaving the page open overnight, the browser is nearly unusable the next day. I tried to strip my own Javascript down and rely mostly on what's provided by tapestry, tried to set several variables (including the links' _tapestry.zoneManager) to null before updating the zone content, but all to no avail. The problem can be reproduced on multiple browsers, such as FF 3.6, Safari 4.0.5 and Chrome 4.1. So finally I tried to put up a simple webapp with just one page and one grid with fake data and a simple JS that "clicks" one of the sorting or paging links every 0.5 seconds. In fact, I overrode Tapestry.Initializer.linkZone to observe a custom event that I fire from my JS. The webapp's source is available as zip file from [1]. Maybe someone has an idea what I'm doing wrong, how I could prevent the memory from being wasted or maybe someone could suggest a method to find out where the memory is going. I was not able to find a tool to show me an overview over what objects the browser holds in memory. Any help is highly appreciated.
Regards, Jochen [1] http://www.file-upload.net/download-2369007/zonetest.zip.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
