Firebug 'Console' filling with 'Strict' warnings

139 views
Skip to first unread message

ramasaig

unread,
Aug 24, 2011, 9:13:07 AM8/24/11
to Firebug
I was more than a little flummoxed when I started getting messages
that Firefox 6 was using 100% of the CPU. Eventually I traced it to
the Firebug Console, where I'd inadvertently got 'Strict Warnings
(Performance Penalty)' checked. The pane is full of the following
warning, endlessly repeated:
"reference to undefined property fbs.breakpoints[url]
[Break On This Error] return fbs.breakpoints[url];
firebu...vice.js (line 3319)
<System>"
'Info' shows that the Firebug log capacity has been exceeded by some
colossal and ever increasing number.
Looks like a bug in Firebug, I thought. I'm using Firebug 1.8.1.
Firefox 6, WinXP SP3.

However, for me this is only occurring on one web page (http://
www.holidaymull.co.uk). I'm web-master for this site, so it concerns
me very much. The culprit seems to be a vertically scrolling 'News"
marquee (Javascript, of course). The marquee has been running for a
long time now (periodic update of content, of course, but no changes
to the script), but it's only very recently that I've noticed this
effect in Firebug. The same happens on my 'localhost' version of the
site. There are no break-points set, but there is a 'setTimeOut' call;
could that have the same effect ?

The CPU overload problem goes away if I disable 'Strict Warnings', of
course.
I have not been able to produce the same effect on my Win7 laptop.

Is it something I can do anything about, or just a feature in
Firebug ?

Regards,

Tim Dawson






Jan Honza Odvarko

unread,
Aug 25, 2011, 3:10:51 AM8/25/11
to Firebug
On Aug 24, 3:13 pm, ramasaig <t...@ramasaig.com> wrote:
> I was more than a little flummoxed when I started getting messages
> that Firefox 6 was using 100% of the CPU. Eventually I traced it to
> the Firebug Console, where I'd inadvertently got 'Strict Warnings
> (Performance Penalty)' checked. The pane is full of the following
> warning, endlessly repeated:
> "reference to undefined property fbs.breakpoints[url]
> [Break On This Error] return fbs.breakpoints[url];
> firebu...vice.js (line 3319)
> <System>"
> 'Info' shows that the Firebug log capacity has been exceeded by some
> colossal and ever increasing number.
> Looks like a bug in Firebug, I thought. I'm using Firebug 1.8.1.
> Firefox 6, WinXP SP3.
This is probably related to: http://code.google.com/p/fbug/issues/detail?id=4726
Honza

> However, for me this is only occurring on one web page (http://www.holidaymull.co.uk). I'm web-master for this site, so it concerns

gswkaiser

unread,
Aug 25, 2011, 9:58:18 AM8/25/11
to Firebug
If you install the Developer Toolbar, you can disable the strict
Javascript messages.

On 24 Aug., 15:13, ramasaig <t...@ramasaig.com> wrote:
> I was more than a little flummoxed when I started getting messages
> that Firefox 6 was using 100% of the CPU. Eventually I traced it to
> the Firebug Console, where I'd inadvertently got 'Strict Warnings
> (Performance Penalty)' checked. The pane is full of the following
> warning, endlessly repeated:
> "reference to undefined property fbs.breakpoints[url]
> [Break On This Error] return fbs.breakpoints[url];
> firebu...vice.js (line 3319)
> <System>"
> 'Info' shows that the Firebug log capacity has been exceeded by some
> colossal and ever increasing number.
> Looks like a bug in Firebug, I thought. I'm using Firebug 1.8.1.
> Firefox 6, WinXP SP3.
>
> However, for me this is only occurring on one web page (http://www.holidaymull.co.uk). I'm web-master for this site, so it concerns

ramasaig

unread,
Aug 25, 2011, 1:28:00 PM8/25/11
to Firebug
Thank you. Yes, I'd done that, and of course all the warning messages
stopped.
However the nature of the warnings seemed to indicate a problem with
Firebug, not my script, so I thought I should report it.

Tim Dawson

Jan Honza Odvarko

unread,
Aug 26, 2011, 3:22:00 AM8/26/11
to Firebug
On Aug 25, 7:28 pm, ramasaig <t...@ramasaig.com> wrote:
> Thank you. Yes, I'd done that, and of course all the warning messages
> stopped.
> However the nature of the warnings seemed to indicate a problem with
> Firebug, not my script, so I thought I should report it.
This is related to http://code.google.com/p/fbug/issues/detail?id=511

Honza
Reply all
Reply to author
Forward
0 new messages