Site constantly attempts to load a 2nd page?

[RazberyBandit]

It seems any time I load the homepage, an article, the forums, or anything, my browser loads the page then immediately begins loading a whole new page that never finishes. Even on a fresh TH homepage load with a clear FF cache, the homepage loads and displays momentarily, then goes blank while attempting to load something (another page?) that never finishes. I think it's another page because I can actually hit the "Back" button despite having gone to no other site. (Proven by loading the main page and several links on it within new tabs.)

I'm still using the old homepage layout, if it matters. (I don't use "social media" so I don't need those features.) As mentioned, this is happening in Firefox. It may be worth mentioning that I have the Ad-block Plus add-on installed and enabled. (Sorry, but it truly is a necessity for safer browsing.) I see the "new home page is in it's second beta" message, so perhaps that's causing the problem.

Edit: It seems that perhaps clicking the "X" next to the "new home page" message may have cured the problem...

Edit 2: A "News" link on the TH site from the TG site just did it as well. The new page that loads seems to be completely blank, but never stops loading. Once I hit the "Back" button, it's fine, and it doesn't repeat and hasn't occurred again. Strange...

 

[RazberyBandit]

This just happened again following a "Vendor Voice" link. This "secondary page" has been loading for more than 5 minutes and still hasn't completed, with Firefox claiming it's "Waiting for 209.15.236.80" in it's progress bar. I apologize for not having noticed that before.

I'm not sure if that's one of your IP addresses or not, but after a simple tracert, here are the last 6 hops:
11 110 ms 115 ms 115 ms nlayer-level3-10ge.Chicago1.Level3.net [4.71.100.62]
12 130 ms 132 ms 127 ms 10ge.xe-0-2-0.tor-1yg-cor-1.peer1.net [216.187.114.142]
13 130 ms 130 ms 108 ms 10ge.xe-0-2-0.tor-1yg-dis-1.peer1.net [216.187.114.50]
14 133 ms 124 ms 122 ms 10ge.xe-1-3-0.tor-20p1ops-dis-2.peer1.net [216.187.114.190]
15 125 ms 127 ms 128 ms 10ge.tor-20p1ops-dis-1.peer1.net [216.187.114.105]
16 129 ms 127 ms 129 ms 209.15.236.80

Trace complete.

As you can see, I can reach that IP address but cannot resolve it.

 

[raymonkey]

I am getting the same thing

 

[Guest]

Spoiler

I am getting the same thing as well. Everytime I load an article, the page loads then immediately loads another page (ad?????). The only way I can stop it is by hitting Esc to prevent the load of the second page. Need to fix this!!!!

 

[RazberyBandit]

This is still happening! I just tried a search and the result page did it immediately. I opened a news link (the Tom's, Google, Facebook IPv6 one) in a new FireFox tab and it did it as well. It's the same "Waiting for 209.15.236.80" completely blank page that never actually loads. What gives Tom's?

 

[jpishgar]

I'll send this up as a bug. Looks like it could be an issue with either an ad network or a temporary server glitch.

 

[RazberyBandit]

Thanks Joe. Hopefully this issue will be solved quickly. Anything I can do to help, just ask.

 

[jpishgar]

Much obliged for reporting the issue. The devs have identified the problem and are now working to resolve it. Should be good by later tonight, early tomorrow morning at the latest.

 

[RazberyBandit]

JP. While I hate to dig this up, something similar has been occurring all day today.

Just about every article, as well as individual pages withing them, has been loading a completely blank page for me today. Repeated refreshing affected pages eventally results in them displaying correctly. The entire site seems affected, including TH, THG, and their respective forums.

I'm still running the same setup as before: FF 3.6 w/ Ad-block Plus active.

 

[jpishgar]

I'll follow up on this and see if there's anything that can be done. Are you still getting a "Waiting for..." message after the blank? Could you run another traceroute?

 

[RazberyBandit]

There was no "Waiting for..." message as before. The pages were simply empty. It seems to have cleared up overnight, though. I haven't had any issues at all today.