Page 1 of 2
A script on this page may be busy... Script: chrome://noscri
Posted: Fri Oct 09, 2009 5:26 pm
by tryan87
I am receiving the following error while trying to refresh my igoogle page.
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: chrome://noscript/content/RequestWatchdog.js:1082
I think the portlet that is causing the conflict is
http://www.gocomics.com/ because it is the only element on the page that did not refresh. I recently updated to Firefox 3.5.3 and NoScript 1.9.9.07. I also change the dom.max_script_run_time from 10 to 20 in an effort to give the script more time, but that didn't work.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Sun Oct 11, 2009 1:02 pm
by SteveG
I am getting this same error with almost every refresh. I am not running the gocomics portlet mentioned below.
I have updated Firefox and NoScript to latest versions.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Sun Oct 11, 2009 2:26 pm
by therube
See if turning off Chat makes a difference.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Sun Oct 11, 2009 3:02 pm
by SteveG
I signed out of Google Chat and still see the same Unresponsive Script warning.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Sun Oct 11, 2009 3:27 pm
by Giorgio Maone
I added the gocomics gadget to my IG page but cannot reproduce.
Could you upgrade to
latest development build 1.9.0.9 and check if the problem persists?
If it does, could you look for any [NoScript XSS] line in
Tools|Error Console?
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Mon Oct 12, 2009 2:22 am
by theqwert
I get the same issue with
these two gadgets being the ones not loaded. They are the first in the first column, and first in the second column, respectively. Oddly, the second instance of the second gadget always works fine.
It seems to occur after a period of browsing, usually taking over 10 page loads for me, and closing FF resets it. An easy way to reproduce is to open and close iGoogle in a tab until it errors out. Interestingly, allowing scrips globally does NOT fix the issue, while disabling NS does, which also dramatically boosts the load-time of iGoogle in general.
I get this message in the error console's "Messages' tab, only when the error window appears:
Code: Select all
[NoScript DOS] Aborted potential DOS attempt: {GET http://8g3rfsai4nr2fdeondufecjdo7qlrh4r.ig.ig.gmodules.com/gadgets/ifr?view=home&url=http://hosting.gmodules.com/ig/gadgets/file/116754416080903249690/farkfeeds.xml&nocache=0&up_tabFontSize=0.7em&up_showFeedDesc=0&up_showTimestamp=0&up_showSourceArticle=0&up_feed1=http://www.fark.com/fark.rss&up_feedTitle1=Not+News&up_feed2=http://www.fark.com/sports/fark.rss&up_feedTitle2=Sports&up_showSportsTab=0&up_feed3=http://www.fark.com/business/fark.rss&up_feedTitle3=Business&up_showBusinessTab=1&up_feed4=http://www.fark.com/geek/fark.rss&up_feedTitle4=Geek&up_showGeekTab=1&up_feed5=http://www.fark.com/showbiz/fark.rss&up_feedTitle5=Showbiz&up_showShowbizTab=1&up_feed6=http://www.fark.com/politics/fark.rss&up_feedTitle6=Politics&up_showPoliticsTab=1&up_feed7=http://www.fark.com/music/fark.rss&up_feedTitle7=Music&up_showMusicTab=0&up_feed8=http://www.fark.com/video/fark.rss&up_feedTitle8=Video&up_showVideoTab=1&up_feed9=http://www.foobies.com/foobies.rss&up_feedTitle9=Foobies&up_showFoobiesTab=0&up_entries=9&up_renderHtml=true&up_selectedTab=2&lang=en&country=us&.lang=en&.country=us&synd=ig&mid=94&ifpctok=4564998835306058736&exp_split_js=1&exp_track_js=1&exp_ids=17259,17315,300667&parent=http://www.google.com&refresh=3600&libs=core:core.io:core.iglegacy#st=c%3Dig%26e%3DAPu7icrJUA1OQM3ceB8yVLMJBOHi5DYKAw8RbmZAt9vbEk3YUyXPtfiH3XJfy4POOKetQQSizZFoJiKAbLW3VsjW2nKYHnehFN/vUMZVDYcyw%252BtWRmW1H1wkfB/Bv4mG5QvQdjtKwcik&gadgetId=111901928688144469149&gadgetOwner=101413561995882255650&gadgetViewer=101413561995882255650&extern_js=/extern_js/f/CgJlbhICdXMrMNIBOAEsKzDYATgBLCsw2gE4ACwrMNsBOAEs/fWzgRbX4nIM.js&is_signedin=1&is_social=1 <<< http://www.google.com/ig, http://www.google.com/ig}
(function () {return this.filterXSS(abeReq);})
EDIT: the Dev build shows no improvement.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Mon Oct 12, 2009 5:17 am
by Tom94022
I am getting the same error and not using Gocomics.
If anything it is the BBC News Gadget in iGoogle, at least that seems to be the gadget that takes long to load
Tom94022
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 12:56 am
by theqwert
Problem still persists on 1.9.9.11, would love to be able to use NS again.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 6:48 am
by Giorgio Maone
@
theqwert:
I'm still struggling to reproduce, but I suspect the following line in
NoScript Options|Advanced|Exceptions should do the trick:
Code: Select all
^@https?://www\.google\.com/ig(?:/|$)
[edit]:
corrected originally wrong exception syntax.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 6:10 pm
by travelgirl
have tried the suggestions listed above (including ^@https?:www\.google\.com/ig/ in both jar and xss exceptions) to no avail. my problem gadgets are eBirds News and goComics...
fyi - using 1.9.9.07. this has been problematic for several months... just installed 1.9.9.11 - same problem
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 6:44 pm
by Giorgio Maone
@travelgirl:
could you show me the [NoScript XSS] messages you get in Tools|Error Console?
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 7:11 pm
by travelgirl
i wish these things were time-stamped
after clearing the cache, i went to the iGoogle page once more. about 150 errors appeared, mostly for undefined or unknown properties, errors in parsing values, and expected declaration issues. the errors are:
Error: gadgets.config is undefined
Source File:
http://f5hor2frqlsrrh5ve178e2fa7234covj ... s_social=1
Line: 436
Error: gadgets.Prefs is undefined
Source File:
http://f5hor2frqlsrrh5ve178e2fa7234covj ... s_social=1
Line: 1396
Error: gadgets.Prefs is undefined
Source File:
http://ig.gmodules.com/gadgets/ifr?view ... signedin=1
Line: 458
Error: gadgets.Prefs is undefined
Source File:
http://ig.gmodules.com/gadgets/ifr?view ... signedin=1
Line: 475
Error: gadgets.Prefs is not a constructor
Source File:
http://f5hor2frqlsrrh5ve178e2fa7234covj ... s_social=1
Line: 1432
Error: gadgets.util is undefined
Source File:
http://f5hor2frqlsrrh5ve178e2fa7234covj ... s_social=1
Line: 1497
Error: _IG_Prefs is not defined
Source File:
http://ig.gmodules.com/gadgets/ifr?view ... signedin=1
Line: 488
Error: gadgets.util is undefined
Source File:
http://ig.gmodules.com/gadgets/ifr?view ... signedin=1
Line: 659
and finally
Error: Permission denied for <
http://talkgadget.google.com> to call method Location.toString on <
http://www.google.com>.
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 7:33 pm
by Giorgio Maone
None of these warnings are related to NoScript's XSS filters.
You can filter the relevant lines by clicking on the "Messages" button (blue icon) in Tools|Error Console: I'm after those lines starting with [NoScript XSS].
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 7:54 pm
by travelgirl
the only [NoScript * ] found in messages deals with HTTPS for a different webpage... there are no obvious messages for XSS errors. there are a few ABE messages, but none of those deal with iGoogle...
Re: A script on this page may be busy... Script: chrome://noscri
Posted: Wed Oct 14, 2009 8:08 pm
by Giorgio Maone
But could you reproduce the issue during the current session?
And how do the ABE messages look like?