Command file "chrome://vidbar/content/db.js:312" does not respond
I get a message (in Finnish):
"Tällä sivulla oleva komentotiedosto on varattuna tai ei enää vastaa kutsuihin. Voit pysäyttää komentotiedoston suorittamisen tai odottaa sen suorituksen valmistumista.
Komentosarja:chrome://vidbar/content/db.js:312"
the translation of which is rohgly "The command file on this page is busy or does not rstpond anymore. You can either stop it or wait until it is executed. The command script is: chrome://vidbar/content/db.js:312"
I get the message always (but not only) when I start Firefox.
Все ответы (2)
This issue can be caused by an extension that isn't working properly.
Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
- Don't make any changes on the Safe mode start window.
- https://support.mozilla.com/kb/Safe+Mode
If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.
- Use "Disable all add-ons" on the Safe mode start window to disable all extensions.
- Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")
In Firefox 4 you can use one of these to start in Safe mode:
- Help > Restart with Add-ons Disabled
- Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)
Thanks for your reply! I started Firefox in safe mode, and really, didn't get the message then. So, it seemed that the problem really comes with one of the Add-ons.
So, I tried to find out which Add-on is the one causing the error message. I returned to normal mode, disabled all the Add-ons one by one, and restarted Firefox after each change - and got the same message again :(
However, when I then went to safe mode, and told to disable all Add-ons permanently, the message vanished. And now, even if I went and turned all the Add-ons on manually one by one, the message still did not come back... but unfortunately the problem was now left unexposed...