Brilliant!

[pd]

Thank you and congratulations for these new features. Combine this
with the Hueyfix that really hits the memory leaks of add-ons for
dead, this is a fantastic month for Firebug. I super-tempted to even
run a Nightly at work to take advantage of this combination.

[Sebo]

Thanks man, we're putting a lot of effort in to get new features in.
It would be great if you could try it out and gave us some feedback.

Sebastian

[Jan Honza Odvarko]

Thanks for the support!
Honza

[pd]

Hi Seb, Jan. I've got some very disappointing news. I tried Firebug a couple of times just now and it is running terribly. I'm not sure if I've done something wrong but I don't think so. I even just found a really nasty slow-crawl memory-ballooning bug - my modem config pages left running on it's status page, of all things - anyway I tried to open Firebug 1.10.0a8 in this Nightly I'm running (which I believe has the Hueyfix) and it a) Takes at least 30 seconds to load, if not longer; b) locks the whole browser UI whilst it's loading; c) can make the browser crash to the point of Not Responding.

I'm really not sure what the issue is. I don't remember ever seeing this before and with respect, I've seen Fire(fox|bug) do *a lot* of crazy stuff over the years. I'm running:

15.0a1 (2012-05-13)

and a whole series of add-ons. However I've been running the same set of add-ons for a while, such as when using previous 1.10 alphas and never seen this (though I wasn't running Nightlies with previous alpha versions.

I can test with a naked profile and see if any add-ons are conflicting but I've been keeping up to speed with MemShrink and I checked that all my add-ons are compiled with the latest Jetpack SDK or otherwize are not Jetpack based. There's a list going around and I found one new add-on called au-revouir-utm was on the list so I deleted it from my system.

I'd really hoped that the Hueyfix would resolve all of Firebug's memory leaking problems. Perhaps those leaks are now solved but another huge issue has arisen?

Thanks
pd

[Jan Honza Odvarko]

> I can test with a naked profile and see if any add-ons are conflicting but

Yep, I'd recommend that in any case.

I have recently filled this bug, which is related to "freezing
Firefox"
https://bugzilla.mozilla.org/show_bug.cgi?id=754201

Are you on Linux?

Does the problem happens for you even if you have Console, Script and
Net disabled?

Weird is that I am running Firebug (SVN HEAD) on Nightly all the time
and
I don't see any huge delays....


Honza

[pd]

Hi Jan

I'm running Windows XP all patched.

I just checked Firebug's loading performance using a new profile and Nightly (via Mozilla Profile Manager) and the good news for everyone else is that it's running fine. Caveats though: I only had a couple of tabs open whereas my previous experience in this current older profile was with about 22 open. Secondly it was a very quick test. I did use the same site though.

*sigh*

Looks like it's back to the old "you've got too many add-ons" rank PITA. Boy I really wish my patience with Mozilla's borked add-on infrastructure was rewarded more often.

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 (when not using one of my old profiles or conflicting extensions)? I'm really very excited by the potential of the Hueyfix because, to be honest, I think all the native web developer tools momentum has been secretly based on the impression that Firebug's memory leaks were terminal. If the vast majority of Firebug's memory leaks are now behind it, the future Firebug vs native webdeveloper tools looks much better for Firebug :)

LONG LIVE THE 'BUG!

[Jan Honza Odvarko]

> 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.

Honza

[pd]

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.

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.

Thanks
pd

[Jan Honza Odvarko]

On May 15, 12:41 pm, pd <an0n1m...@gmail.com> 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