Hi, the memory leak may come from your code, make sure you call element.destroy() of every element you create as soon as they are no longer used.
On Mon, Jun 28, 2010 at 2:28 AM, Marc Weber <[email protected]> wrote: > Excerpts from Trevor Orr's message of Sun Jun 27 22:21:11 +0200 2010: > > What I would like is suggestions of what kind of things I should be > looking > > at? > > Hi Trevor Orr. > > Firebug can profile JS. So if run that profiling for some secs, wait > those 8 min and do it again you should be able to see what is consuming > that much CPU. Maybe some arrays are filling up and iterating over them > over and over again takes more and more time? > > Of course there cane be many more causes. I'd check this obvious first > though because you said the slowness can be seen on different browsers. > > Marc Weber > -- http://tbela99.blogspot.com/ fax : (+33) 08 26 51 94 51
