Message from discussion
Brilliant!
Received: by 10.52.24.68 with SMTP id s4mr4437721vdf.3.1337004339954;
Mon, 14 May 2012 07:05:39 -0700 (PDT)
X-BeenThere: firebug@googlegroups.com
Received: by 10.52.88.40 with SMTP id bd8ls1590766vdb.0.gmail; Mon, 14 May
2012 07:05:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.68.141 with SMTP id w13mr260099vdt.18.1337004331606; Mon,
14 May 2012 07:05:31 -0700 (PDT)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
odva...@gmail.com designates internal as permitted sender)
smtp.mail=odva...@gmail.com; dkim=pass
header...@gmail.com
Received: by d10g2000vbw.googlegroups.com with HTTP; Mon, 14 May 2012 07:05:31
-0700 (PDT)
Date: Mon, 14 May 2012 07:05:31 -0700 (PDT)
In-Reply-To: <336043.21.1337001847442.JavaMail.geo-discussion-forums@pbckt5>
References: <a1b595c2-765e-4b2b-986e-c91a72f8cc8d@n5g2000pbg.googlegroups.com>
<26007268.1204.1336861519716.JavaMail.geo-discussion-forums@vbyb13>
<11522436.40.1336998667132.JavaMail.geo-discussion-forums@pbbrq3>
<5c8c8250-bb52-4834-a1e1-c036cce833fd@v10g2000vbe.googlegroups.com> <336043.21.1337001847442.JavaMail.geo-discussion-forums@pbckt5>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20100101 Firefox/12.0,gzip(gfe)
Message-ID: <df8b8be5-0a6a-41ff-9831-63eaeac81ebc@d10g2000vbw.googlegroups.com>
Subject: Re: Brilliant!
From: Jan Honza Odvarko <odva...@gmail.com>
To: Firebug <firebug@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
> 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 forwa=
rd
> 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
On May 14, 3:24=A0pm, pd <an0n1m...@gmail.com> wrote:
> 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 op=
en
> whereas my previous experience in this current older profile was with abo=
ut
> 22 open. Secondly it was a very quick test. I did use the same site thoug=
h.
>
> *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 forwa=
rd
> in terms of memory leak reduction in Firebug (when not using one of my ol=
d
> profiles or conflicting extensions)? I'm really very excited by the
> potential of the Hueyfix because, to be honest, I think all the native we=
b
> 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!
>
>
>
>
>
>
>
> On Monday, May 14, 2012 10:40:09 PM UTC+10, Jan Honza Odvarko wrote:
>
> > > I can test with a naked profile and see if any add-ons are conflictin=
g
> > 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=3D754201
>
> > 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
>
> > On May 14, 2:31 pm, pd <an0n1m...@gmail.com> wrote:
> > > 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 t=
his
> > > 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 neve=
r
> > 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 conflictin=
g
> > but
> > > I've been keeping up to speed with MemShrink and I checked that all m=
y
> > > 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 memo=
ry
> > > leaking problems. Perhaps those leaks are now solved but another huge
> > issue
> > > has arisen?
>
> > > Thanks
> > > pd
>
> > > On Sunday, May 13, 2012 8:25:19 AM UTC+10, Sebo wrote:
>
> > > > 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=
.
>