error messages on the LQ site

atterkop · 01-23-2016, 03:41 AM

When I reverse back through a chain of pages (browser "<= Back" button) on your site, most often I get the following message.

Quote:

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://ap.lijit.com/sync:2

[X Stop Script] [v/ Continue]

And a similar message, but less frequently for this script.

Quote:

https://pixel.adsafeprotected.com/jload?anId=6279&pubId=DoubleClick_Bid_Manager&placementId=hrbcpa&adsafe_par&uId=14291ca9bda8eee&impI d=cm-50385705754_1453541416&adsafe_par&bidurl=https://www.linuxquestions.org/questions/profile.php%3Fdo%3Dprivacy?:167

The browser will freeze for as much as a minute before the error message actually appears. I have been getting similar messages on several sites recently and blame advertsments and html5.

ButterflyMelissa · 01-23-2016, 04:46 AM

Quote:

blame advertsments and html5.

hmm, did you install adblock plus and ghostery already?
give 'em a whack, could help...
By the way, welcome to the forum

Melissa

ondoho · 01-23-2016, 08:17 AM

yep.
adblock (or block origin these days), noscript and request policy.
the latter 2 are a PITA (<= a major pain in the backside) to use, but worth the effort in the long run.
reduces bandwidth and computer resources, increases privacy.

atterkop · 01-23-2016, 01:13 PM

Thank you both.

I blame html5. At least with html4 I eliminated the worst offenders simply by not having Adobe/Macromedia Flash installed.

jeremy · 01-23-2016, 02:12 PM

I'm not able to reproduce this, but I'll look into it further.

--jeremy

astrogeek · 01-23-2016, 02:17 PM

Also, what browser and version are you using?

My recent experience with Firefox has been that new scripts break in older versions of the browser in just that way - they become unresponsive (probably related to responsive web design).

So if you are running an older Firefox you might try an updated version.

atterkop · 01-23-2016, 03:32 PM

>> astrogeek

I am using Seamonkey 2.20, just recently upgraded from v1.0b. I tried v2.39 but didn't like it.

With some difficulty I just installed Adblocker and Ghostery. Finding a version of Abblocker combatable with v2.20 of Seamonkey took some time (Adblock Plus 2.3 for Firefox). I have not (in this little time since) had a stopped script here at LQ or elsewhere.

My original thought was that the advertisers were getting out of hand and might need a good slap.

ondoho · 01-23-2016, 06:50 PM

erm. what distro are you running?
how did you install seamonkey?
you should probably use the version that is in the repos. on archlinux that's 2.39.

i mean, incompatible software can also cause difficulties.

frankbell · 01-23-2016, 08:37 PM

I just backed through eight pages (as far as I could go without leaving the site) with Seamonkey 2.31 with NoScript installed and set to allow all on LQ on Slackware --Current and was not able to reproduce OP's problem.

I have encountered that error from time to time, most often on newspaper websites.

atterkop · 01-23-2016, 11:05 PM

>> ondoho

Distribution is Slackware 14.1, which ships Seamonkey 2.21, but for some reason had to revert to an earlier version.

I have been using 2.20 for quite some time and these problems are not new, but until I was bouncing around this site were fairly rare.

PS - I used the quote tags very deliberatly. The first encloses the text from a dialog (popup warning) box, not an error log. The second encloses only the http address of a second guilty script and nothing more. I did put some thought into it, and judged that code tags were not suitable (since "code" describes neither) and quote tags more appropriate for both.