Something about this section of the forum makes Google Chrome choke with a “This page is unresponsive” error. If I continue to click WAIT, the problem will resolve.
Internet explorer doesn’t give errors like that (ever, even if it’s really broken) but it still takes a LONG TIME (30s+) for the initial forum view to load.
Well, the forum is also pathetically slow on Firefox - its like it has to fetch pictures and pieces of code from 20 different servers and they are all always busy…
The Ideas Lab still causes Chrome 4.0 to lock up while it does *something* in the background.
Duration is usually about a minute (often resulting in Chrome to ask if I want to Kill the tab), which is excessive.
At least Chrome lets you use other tabs; Firefox 3.6 locks up - ‘Not Responding’ - until the page loads, although in that case the page does load faster.
I use Chrome 4 exclusively because for me, its much faster than Firefox. Can you tell me what OS you are using? Also, make sure you have the latest version of Java installed - that makes a big difference.
On mine, it’s hanging on “Waiting for s7.addthis.com,” but I don’t know if that server is unresponsive, or if the forum CGI’s are just hanging before finishing the base HTML build.
I’m running Win7x64. Don’t know off-hand which Java I have… Chrome is, of course, always up-to-date automatically…
I have stopped using the Ideas Lab for the time being because it takes my browser out of action for several minutes, not just the Ideas Lab page but any other WDC forum tab too.
Very frustrating.
-edit-
As a workaround to the Ideas Lab loading time killing all WDC tabs, I’ve found that opening the Ideas Lab in an Incognito tab isolates it and prevents all WDC tabs freezing.
However, there’s still a several minute delay before it loads. If you forget to sign in before browsing to the Ideas Lab, you’ll then need to sit another several minutes after it signs in and reloads the page.
I find it interesting that the forum is now using the very latest version of jQuery… updating simply for the sake of updating, or do they just not have any idea what’s causing the issue? :|