On Jun 18, 10:44 pm, James Olsen <[email protected]> wrote: > Hello, > > I also started encountering issues with Firefox 13.0.1 and FireBug 1.9.2 > this morning, on multiple machines (running Windows 7). However, my error > message is different: > > A script on this page may be busy, or it may have stopped responding. You > can stop the script now, open the script in the debugger, or let the script > continue. > Script: chrome://firebug/content/firefox/tabWatcher.js:772 > > It does not make a difference if I choose Continue, Debug script, or Stop > script. I click the button, FireFox attempts to do something for a few > seconds and is unresponsive, ignoring user interactions, until the message > pops up again. The only way to get past this error is to terminate FireFox > and relaunch it. Admittedly, that's not a very good work-around. > > I don't have an exact trigger, it seems like clicking on a link on a page > can do it. The tab title says "Connecting..." and the normally-spinning > progress animation is not animated. The main FF content pane will sometimes > white-out and FF will become unresponsive if I try to do anything with the > browser after clicking any of the three options or closing the alert. After > a few seconds of FF ignoring me, I'll get the same script message about > tabWatcher.js. There does not appear to be any way of using FireFox once > this happens. > > Someone I work with, using FF on a Mac, is also having a lockup issue > starting this morning. Unfortunately, I cannot confirm the exact error > message (if it is tabWatcher or something else) at this time. > > It does not happen with all links or all clicks to the same link. It may > work successfully a time or two before acting up. I currently have two tabs > open to different pages on the same site. I don't understand at the moment > what the problem is or how to provide concrete steps to reproduce. I tried > downgrading to FF 13.0 but the problem persists. Perhaps that means that > problem is somehow in my profile or settings and introduced with 13.0.1. > This site uses some YUI, but nothing that should be being executed when > clicking this particular link (if clicking the link is even related to the > actual trigger of this problem) > > I took a peek at the source, and, if I got my hands on the correct version, > line 722 appears to be getting the number of contexts. Having no experience > with the FireBug code or the internals of FireFox, I am not sure without > doing a lot of research what the contexts actually are in this (no pun > intended) context or what might cause the calculation/retrieval of length > to have an issue. > > iterateContexts: function(fn) > { > for (var i = 0; i < contexts.length; ++i) > { > var rc = fn(contexts[i]); > if (rc) > return rc; > } > }, > I know you need STR to really dig into it, but perhaps looking at that line > in tabWatcher might give you some ideas of what time of activities we can > try to generate a reliable set of STR.
Interestingly I am seeing different code at this line: https://github.com/firebug/firebug/blob/firebug1.9/extension/content/firebug/firefox/tabWatcher.js#L772 Anyway, a context represents data object that collects (meta) information about a page (script sources, HTTP activity, etc.). The data (aka document) are consequently displayed in Firebug panels (aka views). The context is created for every page where Firebug is active (opened). Do you experience the problem when using Firebug 1.10a11? (use in a test profile now) http://getfirebug.com/releases/firebug/1.10/firebug-1.10.0a11.xpi 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
