Loading Profile...
javascript slow
The morning of April 23th (Chicago) the javascript started causing problems for me on kotaku and jalopnik. The previous day all was fine. It continues to this day. I have to use firefox 2.0.0.20. The problem is with such a system:
CPU: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (2660.02-MHz 686-class CPU)
real memory = 2145390592 (2046 MB)
FreeBSD 6.3-RELEASE-p5 (32-bit)
My profile (caches cookies etc) is on an NFS mount, I tried a new profile on a local SATA disk and the problem persists.
A great way to see the problem is to open jalopnik.com in a window. Then middle click to open a link to a jalopnik story in a new tab. While that tab is loading scroll up and down with the scroll wheel. Soon the jalopnik main page will stop scrolling. At that point firefox will become completely unresponsive. After a number of seconds the new tab will get focus and there will be a dialog about a long running script and if you want to stop it. I click yes and then I can use the browser again (unless it crashes, see below). Sometimes the browser will be unresponsive for 5 seconds or so and the dialog will not pop-up and I will be able to use the browser again.
Often it crashes eventually after I have a sufficient number of tabs (it depends often after ten or so) to jalopnik and kotaku open simultaneously, with this message in the xterm window:
$ firefox
The program 'gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 5459458 error_code 11 request_code 53 minor_code 0)
I have installed the no-script extension and now I have no problems with kotatku and jalopnik, but I cannot read the comments then. The moment I have enabled javascript from kotaku.com or jalopnik.com with the options button at the bottom of the page, the problem returns.
I have tried rebooting, with no improvement. I only see the issue on this machine, for example with a much slower OS X 10.5 running 1 GHz PPC Macintonsh, there are no problems.
Also needing to have javascript and an account to post a problem report here, not cool. I had to try three times since I could not get the captca to show when I installed no-script in getting my browser to not crash all the time.
CPU: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (2660.02-MHz 686-class CPU)
real memory = 2145390592 (2046 MB)
FreeBSD 6.3-RELEASE-p5 (32-bit)
My profile (caches cookies etc) is on an NFS mount, I tried a new profile on a local SATA disk and the problem persists.
A great way to see the problem is to open jalopnik.com in a window. Then middle click to open a link to a jalopnik story in a new tab. While that tab is loading scroll up and down with the scroll wheel. Soon the jalopnik main page will stop scrolling. At that point firefox will become completely unresponsive. After a number of seconds the new tab will get focus and there will be a dialog about a long running script and if you want to stop it. I click yes and then I can use the browser again (unless it crashes, see below). Sometimes the browser will be unresponsive for 5 seconds or so and the dialog will not pop-up and I will be able to use the browser again.
Often it crashes eventually after I have a sufficient number of tabs (it depends often after ten or so) to jalopnik and kotaku open simultaneously, with this message in the xterm window:
$ firefox
The program 'gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 5459458 error_code 11 request_code 53 minor_code 0)
I have installed the no-script extension and now I have no problems with kotatku and jalopnik, but I cannot read the comments then. The moment I have enabled javascript from kotaku.com or jalopnik.com with the options button at the bottom of the page, the problem returns.
I have tried rebooting, with no improvement. I only see the issue on this machine, for example with a much slower OS X 10.5 running 1 GHz PPC Macintonsh, there are no problems.
Also needing to have javascript and an account to post a problem report here, not cool. I had to try three times since I could not get the captca to show when I installed no-script in getting my browser to not crash all the time.
I’m frustrated
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I would like to add that I tried consumerist.com and they do not have the problem. They seem to use much older versions of the scripts that the sites that are still gawker use. -
Inappropriate?I've decided to just add kotaku.com to the restricted sites list to solve this problem. That way any other sites that know how to properly test/profile their page performance can still run javascript, but I don't have to deal with the random lag while trying to simply scroll up/down the page. I was going to say that the down side to this solution is that the comments don't load anymore, but then I got to thinking about the quality of most of the comments that I've actually seen on Kotaku, and I realized that not having the comments load is actually a bonus.
I’m done waiting.
-
Inappropriate?Problem solved, but you might need to clear browser cache.
To do so, load the site in your browser (e.g. lifehacker.com):
- IE press CTRL+F5
- FF press SHIFT+reload
- Safari - select Safari menu/Empty Cache; or SHIFT+reload
The company says
this solves the problem
EMPLOYEE
