Chủ đề này đã được lưu trữ. Vui lòng hỏi một câu hỏi mới nếu bạn cần giúp đỡ.
firefox stops responding showing unresponsive script error at tabbrowser.xml line 2255
When firefox is started it gives error regarding unresponsive script at
chrome://browser/content/tabbrowser.xml:2255 since last few days.
Earlier it was working fine
It just shows firefox quick launch lightened up and then fades down and after lots of time screen shows asking for firefox proxy setting. Later on after much trial and error entering proxy settings no window is displayed and firefox. Since I am not able to open firefox, even closing is required to be done by killing process through windows troubleshooting information. Will try if possible later
Tất cả các câu trả lời (13)
i have this prolem too, any ideas?
Unfortunately we had a data base error today and lost some user accounts when we had to go back to our backups. If you have started this thread, your's is one of those. Since we can not recreate your account, please sign-up for a new account here to reply to the forum messages:
You can use the same username and email address as before. We are very sorry for the inconvenience.
Please help have to ask question again due to database error at Mozilla site
Hi priyac, I noticed in another thread you said this earlier today:
"I have installed Adobe Flash player plugins, Shockwave plugins and Silverlight plugins. But the problem still continues to exists. Installing and clean uninstalling also does not help. parent.lock continues to be created and remains after stopping the Firefox forefully by killing the process in Task Manager in Windows 7."
Has the problem changed, or do you still get the unresponsive script error when trying to start Firefox?
What happens if you try to start Firefox in its Safe Mode? To do that, hold down the Shift key when double-clicking the Firefox icon.
In the small dialog that should appear, click "Start in Safe Mode" (not Reset)
Any difference? More info: Diagnose Firefox issues using Troubleshoot Mode.
Tried Safe mode of Firefox, tried running in Safe Mode with Windows 7 also in Safe mode. Removed all extensions. Just yesterday when firefox 25 was released, reinstalled to different directory. Initially started and ran nicely. But after Windows 7 rebooted again the problem repeats. Not even able to click any where on the Firefox window except clicking OK for proxy authentication
Google Chrome works properly but for my office work I need Firefox. Also Firefox 24 was also working properly till few days back (evening of 18 Oct) when I shut off the lid of my laptop and had to leave for home and disconnected the network. Since then this problem has continued to no avail.
Hi priyac, you wrote:
Just yesterday when firefox 25 was released, reinstalled to different directory. Initially started and ran nicely. But after Windows 7 rebooted again the problem repeats. Not even able to click any where on the Firefox window except clicking OK for proxy authentication
Is the proxy authentication dialog something you used to see when using Firefox 24 successfully, or is this new? What do you know about the proxy -- i.e., something for work, a privacy service, no idea, etc.
Proxy server is used daily at work for internet access and we have been using Firefox since version 1.0 somewhere around 2005/6 etc.
For corporate intranet we do not use proxy but for other sites such as gmail, google proxy will be required. But since the day firefox crashed while shutting down I have not been able to use firefox on my laptop. I have to use other means like Chrome, borrow someone's pc for testing.
attached screenshot of firefox window after reinstalling it today again.
The exercise of installing Firefox in a new directory and confirming that it worked, then having problems after restarting Windows suggests that something in the group policy or login scripts applied to your computer by your IT is relevant to this problem.
Your Firefox settings may be modified by changes to any of these files:
- prefs.js (specific to one Firefox profile, constantly updated)
- user.js (specific to one Firefox profile, read at Firefox startup)
- mozilla.cfg file (added to the program folder, read at Firefox startup)
If creating a new profile in your existing Firefox installation does not change anything -- this assumes you can even start Firefox up into the Profile Manager (see: Profile Manager - Create, remove or switch Firefox profiles) -- then a mozilla.cfg file seems most relevant.
You can't simply remove the mozilla.cfg file, but you could view it in a text editor to see what unique settings it may be adding to your Firefox configuration so we have a better idea of what the most relevant preferences are.
Clear the cache and cookies only from websites that cause problems.
"Clear the Cache":
- Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
- Firefox/Tools > Options > Privacy > Cookies: "Show Cookies"
You can remove all data stored in Firefox from a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History > Show All History" or "View > Sidebar > History") or via the about:permissions page.
Using "Forget About This Site" will remove all data stored in Firefox from that domain like bookmarks, cookies, passwords, cache, history, and exceptions, so be cautious and if you have a password or other data from that domain that you do not want to lose then make a note of those passwords and bookmarks.
You can't recover from this 'forget' unless you have a backup of the involved files.
It doesn't have any lasting effect, so if you revisit such a 'forgotten' website then data from that website will be saved once again.
It seems all these issues are related to session hanging after updating when Firefox is closed using Close button at top-right instead of File -> Exit option.
Please check the above issue.
Firefox upto version 22 did not have this problem.
Hi priyac, does the problem only occur in the session immediately after updating Firefox, it's not an ongoing issue?
There certainly is some difference between using the close button (on the Firefox window or on the Windows Task Bar) and using Exit, but what causes Firefox to hang at shut down can be highly dependent on individual system configuration and your stable of extensions, so it could be hard to replicate under laboratory conditions. I wonder whether there is any data recorded by Firefox anywhere that might help?