On Fri, 18 Apr 2008 09:35:38 +0200, Godefroid Chapelle wrote: > Balazs Ree wrote: >> On Thu, 17 Apr 2008 18:09:41 +0200, Balazs Ree wrote: >> >>> Hi Christophe, >>> >>> thanks for your investigation. >>> >>> On Thu, 17 Apr 2008 17:13:11 +0200, Christophe Bosse wrote: >> >>>> Those leaks are very important. I've done a folder_contents which has >>>> many rules for every single row and my IE grow by 5megs on each page >>>> !!! >>> Is this only on IE? And what version exactly? >>> >>> >> p.s. it just occured to me, folder_contents does not use KSS on the >> rows, afaik. >> > I think Christophe has built his own folder_contents with his own KSS > rules.
Ah, sorry. I may have skipped this information from the beginning of the thread. Dear Cristophe, can you help us with tracking down this issue, let me re- formulate the questions I asked in my previous post! It would be essential to get the answers from you. - Does this only happen on IE, and if yes, on which versions exactly? - What makes you believe that uniqueId can be a problem? (Afaik uniqueId is a builtin node attribute on IE, so we never set it on IE, but I may be wrong.) - Can you please check on one of the standard Plone pages instead of a page customized by you (possibly not folder_contents that contains lots of non-kss code), and confirm if the leak happens again? - Can you confirm that when you talk about memory leaks, you talk about memory leaks that survive the next static page load? This is important because this way we do not need to look for our internal data structures, since there is no way they could cause this kind of leak. Thanks for your replies in advance. -- Balazs Ree _______________________________________________ Kss-devel mailing list Kss-devel@codespeak.net http://codespeak.net/mailman/listinfo/kss-devel
