X
Tap here to go to the mobile version of the site.

Support Forum

In attempting to exit my credit union site, I receive an error message:

Posted

"A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: http://www.aftrasagfcu.org/toolkit/presentation/shell/aftrasag/assets/default.js:265."

Is this a Firefox 9.01 problem or a problem of the website? I've never had a problem using Firefox on this site. Thank you.

"A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: http://www.aftrasagfcu.org/toolkit/presentation/shell/aftrasag/assets/default.js:265." Is this a Firefox 9.01 problem or a problem of the website? I've never had a problem using Firefox on this site. Thank you.

Chosen solution

Seems to be a problem with Firefox 9. I see the same on Linux. Firefox 10 betas also has the problem. Firefox 8 and Firefox 11+ (Aurora and Nightly) do not have that problem. So it looks like a bug that has been fixed, but hasn't landed on the Firefox 10 beta branch at least up to now. So there is not much to do about it apart from stopping the script.

Read this answer in context 1

Additional System Details

Sites Affected

http://www.aftrasagfcu.org

Installed Plug-ins

  • Shockwave Flash 11.1 r102
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.
  • 4.0.60831.0
  • Displays Java applet content, or a placeholder if Java is not installed.
  • Google Talk Plugin Video Accelerator version:0.1.43.4
  • Version 1.9.2.1599
  • LogMeIn remote control components
  • Office Live Update v1.0
  • npmnqmp 071102000006
  • iPhoto6

Application

  • User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

More Information

cor-el
  • Top 10 Contributor
  • Moderator
17564 solutions 158859 answers

Chosen Solution

Seems to be a problem with Firefox 9. I see the same on Linux. Firefox 10 betas also has the problem. Firefox 8 and Firefox 11+ (Aurora and Nightly) do not have that problem. So it looks like a bug that has been fixed, but hasn't landed on the Firefox 10 beta branch at least up to now. So there is not much to do about it apart from stopping the script.

Seems to be a problem with Firefox 9. I see the same on Linux. Firefox 10 betas also has the problem. Firefox 8 and Firefox 11+ (Aurora and Nightly) do not have that problem. So it looks like a bug that has been fixed, but hasn't landed on the Firefox 10 beta branch at least up to now. So there is not much to do about it apart from stopping the script.

Question owner

Thanks very much. I will wait for 10. Edit: I meant 11. I'll just wait.

Thanks very much. I will wait for 10. Edit: I meant 11. I'll just wait.

Modified by oldink73