On Thu, Mar 17, 2011 at 12:49 PM, Honza (Jan Odvarko) <[email protected]> wrote: > Are you downloading any files? > Could it be related to > http://code.google.com/p/fbug/issues/detail?id=3123
No, don't think so. No downloads are happening. > Do you experience the problem if you don't have Firebug activated > any for web sites (the status bar or toolbar icon are grey)? No, if I don't enable firebug at all for a site but having it installed no problems arise. > 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. 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.
