ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 2.0.0.22pre problem with Gmail

  • 2 (ردّان اثنان)
  • 0 have this problem
  • 1 view
  • آخر ردّ كتبه the-edmeister

more options

I am getting the following under Firefox (Bon Echo) 2.0.0.22pre and NoScript 1.9.9.77 when try to open Gmail web site:

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.

When NoScript is disabled, Gmail woks fine.

Tried the solution for Firefox 3.5 by changing the setting dom.max_script_run_time to zero, it did not helped.

Operating system

WinXP, SP3

I am getting the following under Firefox (Bon Echo) 2.0.0.22pre and NoScript 1.9.9.77 when try to open Gmail web site: 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. When NoScript is disabled, Gmail woks fine. Tried the solution for Firefox 3.5 by changing the setting dom.max_script_run_time to zero, it did not helped. == Operating system == WinXP, SP3

All Replies (2)

more options

Why are you still using that old version?

Overall, Firefox 3+ versions have a lot less problems with that warning appearing. I don't understand why NoScript would cause that to happen, the whole point of NoScript is to stop javascript from running - might be better answered at the NoScript support forum. - http://forums.informaction.com/viewforum.php?f=3

As far as that dom.max_script_run_time preference, you need to increase the time to lessen the occurrence of that warning appearing; like maybe 30 or 40 seconds.

more options

I’m using this version because it seems the best web browser that can run on P3/700 MHz with 128 MB RAM.

Tried that forum, not much helpful respond from them.

It really takes when NoSript enabled, 30-40 s to log-in to Gmail, and changing: dom.max_chrome_script_run_time to 40 avoid showing that message, but the log-in to Gmail is still slow.