Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Unresponsive script hangs when it occurs before I'm done saving a page

  • 7 одговорa
  • 18 има овај проблем
  • 10 прегледа
  • Последњи одговор послао chrowe

more options

This usually happens on the Savings Bonds web site. I try to save the file but while I'm navigating to the directory and fixing options and the file name, I get "Warning: Unresponsive Script" with options to stop the script or continue, but neither button works because the Save file dialog takes priority. However, the Save file dialog won't complete and the file is not saved. The only thing I've been able to do is to force quit Firefox.

I have extended the time allowed before the warning occurs, but I'd like a better solution.

A jpg showing both dialogs is here.

This usually happens on the Savings Bonds web site. I try to save the file but while I'm navigating to the directory and fixing options and the file name, I get "Warning: Unresponsive Script" with options to stop the script or continue, but neither button works because the Save file dialog takes priority. However, the Save file dialog won't complete and the file is not saved. The only thing I've been able to do is to force quit Firefox. I have extended the time allowed before the warning occurs, but I'd like a better solution. A jpg showing both dialogs is [http://www.liz4cps.com/photos/unresponsive_script_hangs.jpg here].

Сви одговори (7)

more options

Are you waiting until the web page is fully loaded before trying to save it?

more options

Yes, the web page is loaded before I try to save; it is very simple and loads very quickly.

more options

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).

  • Don't make any changes on the Safe mode start window.

See:

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")
more options

The error still occurs in Safe Mode; I did the following:

  1. Restarted in Safe Mode.
  2. Opened my previously saved treasury bonds page.
  3. From above, went to http://www.treasurydirect.gov/BC/SBCPrice.
  4. Clicked on the Save link just above the bond totals (I have bonds listed).
  5. Hit Cmd-S and waited.

The save file dialog came up as expected. After a few minutes, the error message about the unresponsive script warning came up, so I quit out of it.


Thanks for the info on how to debug this; I was hoping it would sort things out.

Измењено од стране liz4cps

more options

Did you close the File picker window after entering a name for the file?

If you leave that window open then you may get such an error, I think that I've seen that happen myself.

more options

I have a Mac; I had to look up file picker!

Today, I just left the default name there and left the file browser (similar to file picker) open to see if it would hang.

The problem I've been having is that by the time I've figured out where to save the file, the name of the file, made sure to add the .html onto the end, check which save type I need, and make sure "web page, html only" is picked, the thing will time out. That sounds kind of dumb but I only do this every 2-3 months, and I was in the habit of checking that information after doing cmd-S. It has caused me to have to restart Firefox the last 2-3 times I've needed to do this.

I have made a plan to do this faster by making a note about it where I save the url I use for this, but this is a bug.

more options

Same problem here, running Snow Leopard 10.6.5 and FF 3.6.12? (Now it is running 3.6.13 after I restarted FF and it ran an update)