Maybe it's because there's a ton of comments to the article. It's probably overloading the memory that Safari is allowed to use. It froze Safari 3.2 for a few seconds while it loaded the entire page.
Locked my whole phone and I had to reboot it. I was also listening to a podcast at the same time. What I find hilarious is that this is an iPhone site!
This didn't crash my Firefox, but my comp hesitated and the CPU usage went way up (and I have a quad core processor). I'm not surprised this page would crash Mobile Safari.
It actually crashed my whole phone. Safari froze up, and I tried to hit the home button and it rebooted. I didn't hold the home button down, I just hit it once and the screen went blank and the next screen was the apple logo!
I don't know if it's related to me testing that link, but right after posting my reply above, I 'locked' my iPhone and took a shower. After the shower, I went to wake the iPhone and the display told me to 'Connect to iTunes' and would only allow emergency calls. After I connected to my computer, it said my phone was 'now activated.' WTF?! I'm glad this didn't take long to fix as I was heading out the door to meet my carpool and didn't have time for any kind of restore. Had I not checked it before heading out, I'd have been without my phone all day.