On May 15, 12:41 pm, pd <[email protected]> wrote: > On Tuesday, May 15, 2012 12:05:31 AM UTC+10, Jan Honza Odvarko wrote: > > > > Jan is the Hueyfix as big a bonus to you as it seems to me? I know we've > > > talked about memory leak issues and you've been trying hard but were > > > finding it difficult AFAIK. Can we really expect a substantial leap > > forward > > > in terms of memory leak reduction in Firebug > > My tests (that I have been using to repro zombie-compartment problem) > > are indicating, that there are no zombies any more. I yet need real > > feedback from users, but my feeling is that all the zombie > > compartments > > problems are fixed, which I think was the main reason why Firebug > > leaked memory. So, yes, it should be great improvement. > > Hi > > That's what I was hoping to hear. Alas I've tested the latest in my Nightly > with a very old profile and I slowly disabled all the add-ons I had > installed except Firefbug. This improved the freezing and/or crashing I was > experiencing but although opening and closing Firebug got faster, it's > still much slower than in a completely new profile as I tested with Mozilla > Profile Manager. Mozilla should do more to promote Moz Profile Manager to > potential testers BTW as it's very handy. Here is a nice wiki page about how to manage Firefox profiles http://support.mozilla.org/en-US/kb/Managing-profiles
> Perhaps just disabling add-ons is not enough? I've seen admissions from > MemShrink that even disabled extensions can cause pain. What do you think > Honza? I could uninstall all my add-ons instead of just disabling them but > I'd rather not. If you disable an add-on, it's disabled and the code is just not executed. I see following options how the add-on could still cause some problems: 1) You did disable the add-on, but didn't restart Firefox. Even if the add-on is marked as restart-less, its code can still be in the memory. 2) The add-on change/broke the user profile. So, even if it's uninstalled the profile is still broken and causes problems. 3) Special case of #2 are preferences, if the add-on modified some prefs they are still modified after disabling. So, the safe way is always testing with a new fresh profile. > I've seen admissions from MemShrink that even disabled extensions > can cause pain. Where did you see it? Honza -- 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 https://groups.google.com/forum/#!forum/firebug
