I found that my Tapestry (4.0.2) application was causing memory leaks in IE.
I spent a lot of time trying to figure out why. I removed many parts from my page so that the page contains only one form with one Select component. It still leaks memory. I checked the Tapestry.js and saw it hooks up three attributes on form: events, onsubmit, onreset. Then, I added dojo.event.browser.addClobberNodeAttrs(form,["events", "onsubmit", "onreset"]) in my page. The IE memory leak went away. I will continue to check memory leaks with my application, if I find anything related to Tapestry, I will post it here. Since Tapestry 4.1 is using dojo. Can I assume that this kind of memory leak will not happen in 4.1? Or, are all Tapestry 4.1 event handlers based on dojo? When will Tap 4.1 be released? How confident the Tap committers feel about Tap 4.1? Thanks. Best Regards, Cliff Zhao
