Flash and Scripting Errors on Chowhound
- Dommy Jul 17, 2013 09:11 PM
In the last week or so, P and I have been having our browsers [Safari Firefox (Mac and PC) and IE] Slow to a halt with scripting errors and Flash problems.
A recent Error that Firefox for Mac displayed was:
"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://choices.truste.com/ca?aid=pott... "
Stopping Flash sometimes fixes the problem but it takes a while for the command to run, if the browser doesn't crash first.
It will be hard since the browsers grind to a halt and the only way to restore is to kill the flash or which gives you a blank space with an error where the ad was or the browser crashes and must be restarted. I'll do my best to get an image. It does take a while for the problems to arise, maybe about 15 minutes of having a Chow/Chowhound page open. I tend to go through the boards and open threads as tabs then look at the threads so I may have 10-15 Chowhound threads open at once, then read them at my leisure. However that is not the way Dommy my wife reads Chowhound and she still has issues.
also experiencing navigation problems using IE10 on a Win7 pc.
CH site navigates fine while reading posts off various boards, then when loading a random post, an Adobe flash ad will load 200+ times. Left clicking (or hovering) on left arrow to navigate back and you'll see the string of ad loads in the history.
Here are the screen shots of the latest occurrence. Note the ads load ok and are Adobe flash for Hilton Hotel brands and LG.
Have Adobe flash player 11.7.700 on this pc.
I have been experiencing the very same thing. In fact, about 45 minutes ago I had to restart to access the site again. Now I know it's not my computer. PC/FF
Yes, I've had the same problem several times over the last couple of days with Flash scripts on chowhound pages.
Similar issue, using Opera browser that's worked flawlessly with Chowhound for months. Nice to know the issue is across multiple browsers -- hope it gets corrected soon.