On Mar 21, 5:12 am, Wolfgang Rosenauer <[email protected]> wrote: > Hi, > > On Thu, Mar 17, 2011 at 4:36 PM, John J Barton > > > > > > > > > > <[email protected]> wrote: > > > On Mar 17, 5:00 am, Wolfgang Rosenauer <[email protected]> wrote: > >> On Thu, Mar 17, 2011 at 12:49 PM, Honza (Jan Odvarko) <[email protected]> > >> wrote: > >> > Any particular steps we could use to reproduce the problem on our > >> > machines? > > >> I do not do any sophisticated stuff. > >> I'm basically using it to watch the console and DOM for debugging a webapp. > >> So only watching the console, looking at some objects and DOM trees > >> already triggers the issue for me. > >> That is not really a new thing but happens for several weeks already > >> with previous FF4 betas and earlier firebug versions. > > >> The memory footprint seems to increase a lot for js/gc-heap if that > >> helps to get an idea. > >> I cannot point to a certain action in firebug which triggers it > >> although it can be seen pretty fast for the UI lag but not instantly. > > > It would be very helpful if you could install Firebug 1.7 into a new > > firefox profile and verify that the problem still occurs. > > I did that and just worked again with FF 4.0 final/rc2 and 1.7b3 and > again UI begins to get sluggish and memory consumption is at 1GB again > (where it was at around 400MB before using Firebug). > All I did was starting Firebug console for a tab, reloading the webapp > a few times, watching errors and modified some internal objects on the > fly.
Ok, so the next step is to create a test case we can reproduce, then post it to http://code.google.com/p/fbug/issues/list jjb > > Wolfgang -- 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.
