On Jun 17, 3:08 am, Sebo <[email protected]> wrote:
> Investigated a bit more and have to revise what I wrote before. The
> change from components to modules causes this problem at the moment
> (even when I already had that problem in an earlier version of 1.6,
> this seemed to be fixed before the change to modules).
> To my questions:
> 1. Ok, the throttle queue is containing the console messages of the
> current browser tab, right? So the messages, that shall be displayed
> inside the Console Panel.

The console messages of the browser tab that is tracked by the context
object containing the queue.

> 2. "return;" wouldn't fix this, because I was having a logical
> problem. The queue CAN contain messages, but it shouldn't be looped
> over more messages than it is containing. The lines 489 and 490 should
> avoid this, though somehow this is breaking. Though I couldn't figure
> out why because of the problem explained 
> inhttp://code.google.com/p/fbug/issues/detail?id=3017.

I fixed the part of 3017 I can understand (R7068). But I kinda doubt
this fixes your other issues.

jjb

>
> John, please tell me, if you can reproduce this.
>
> On Jun 17, 9:54 am, Sebo <[email protected]> wrote:
>
> > The Tracing Console gives me:
>
> > chrome://firebug/content/tabContext.js (486) [...]
> > chrome://firebug/content/tabContext.js (501) [...]
>
> > In line 485 flushThrottleQueue() is checking, if queue[0] is not
> > defined and printing that inside the Tracing Console (your change in
> > r4190 back in September 2009). Though in line 493 you are trying to
> > access this variable.
> > Two questions here:
> > 1. What is the throttleQueue representing? The messages sent to a
> > Panel?
> > 2. Would a simple "return;" after the Tracing Console output fix this
> > problem?
>
> > Sebastian
>
> > On Jun 14, 4:35 pm, John J Barton <[email protected]> wrote:
>
> > > Please run with the Tracing console open and when you see the error,
> > > look for
> > > tabContext.flushThrottleQueue no queue
> > > in the trace. The call stack may give us some clues.
>
> > > jjb
>
> > > On Jun 14, 1:33 am, Sebo <[email protected]> wrote:
>
> > > > Lately I am often seeing the following error inside the Console Panel
> > > > when having "Show Chrome Errors" enabled.
>
> > > > queue[i] is undefined
> > > > chrome://firebug/content/tabContext.js
> > > > Line 493
>
> > > > I am using FF 3.6.3 + FB 1.6 (SVN) under Windows 7.
> > > > Because I don't know at the moment by what this is caused, I can't
> > > > create a test case for this and therefore didn't create an issue yet.
> > > > Instead I wanted to ask first, if somebody else also gets this error
> > > > or can tell me by what this could be caused.
>
> > > > Greetings
>
> > > > Sebastian

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

Reply via email to