On Jan 25, 4:06 pm, nkiesel <[email protected]> wrote: > On Jan 13, 8:00 pm, Pedro Simonetti Garcia <[email protected]> > wrote: > > > A perfect test case is just a minimal HTML+JavaScript file that reproduces > > the problem, that is, that shows a high memory consumption. > > I think I see the same problem: I have to restart Firefox after a day > or two of debugging our dojo-heavy application because Firefox just > becomes dog slow (pages that normally load < 1 second take more than > 10 seconds to load). Given the sate of the app right now, not running > it under Firebug is not really an option but it seems that the > slowdown is way less if I try for some time. Before I start pointing > fingers at firebug: what is the best way to see the increased memory > consumption?
The only way I know is the process explorer in Windows. Beware you will need to the test in a clean firefox profile with only firebug installed if you want to do any pointing ;-). jjb > > </nk> -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
