PDA

View Full Version : episode pages crashing Firefox


gevmage
02-28-2007, 03:14 PM
The individual inDigital episode pages are crashing my browser. Not that main inDigital page, but episode pages like http://revision3.com/indigital/ces2007-2

I'm using the IceWeasel browser, which is Debian's rebranded Firefox, version 2.0.0.1. My machine is a current Debian Unstable running kernel 2.6.18-4-686.

I would assume it's a problem specific to the browser...but I tried it on my wife's Windows XP computer, using Netscape 7.2. Same thing.

Anyone else having this problem? (It worked for me a couple of months ago, I don't know when the change happened.)

tokenuser
02-28-2007, 03:28 PM
No problem in Opera or IE (on XP SP2).

gevmage
02-28-2007, 04:36 PM
No problem in Opera or IE (on XP SP2).

Right, I forgot to mention that. On the same fairly new XP machine where Netscape crashes, IE loads the pages just fine.

By the way, it's all of the episode pages, not just one of them. I've tried clicking on several at random, including early episdoes that I know I've viewed before, but same thing--my browser (Iceweasel/Firefox) crashed hard.

masherscf
02-28-2007, 04:56 PM
Why don't you try using actual Firefox and not the Debian rebranded version. Also, you might try some other flash video sites like YouTube or some other Revision 3 products to test if there is a problem with the InDigital encoding, the embedded player or the flash plug-in.

haanzz
03-01-2007, 08:13 AM
Why don't you try using actual Firefox and not the Debian rebranded version. Also, you might try some other flash video sites like YouTube or some other Revision 3 products to test if there is a problem with the InDigital encoding, the embedded player or the flash plug-in.

Firefox seems to work fine in XP and OS X. Haven't tried a Linux version though...maybe Wil has? I'll ask.

Hahn

gevmage
03-01-2007, 03:00 PM
[I would like to state for the record that if I were listening to someone else report these symptoms, I would think that person either really didn't know what they were doing, or were certifiably insane. Nevertheless, I will report the symptoms as I have observed them.]

Bottom line: The thing that makes the individual episode pages work is to uncheck "Load Images Automatically". Argh.

IT'S NOT JUST INDIGITAL: I went to Diggnations page and the same thing happened on one of their episode pages.

It's not flash: I disabled flash, and the pages loaded just long enough for me to to see the "download plugin" icon and then the browser crashed.

It's not Java or Javascript: I disabled them, and the pages crashed the browser.

I have now done this on three different OS/browser combinations with the same result:
Debian Unstable with IceWeasel(Firefox) 2.0.0.1
Windows XP with Netscape 7.2
Ubuntu 6.06 LTS with Firefox 1.5.0.9

So...has revision 3 changed the formatting templates for their episode pages with a new image, in, say, the last 2 months?

gevmage
03-01-2007, 03:45 PM
I tried to reproduce the error by downloading the page, with prerequesites with wget. However, I can't seem to get the page to render properly when served from my machine. So I can't check directly.

The only possible clue that I have is two images that were downloaded as prerequesites to the episode 11 page that I was using as my test case. I looked at those images in my browser both locally and directly from the indigital page. The one possible clue is that the image
http://www.revision3.com/static/images/arrow_up.png
does not load properly in my browser. When loaded like that, directly, it doesn't crash the browser, but it doesn't show anything.

Sorry I don't have any more useful information.

chuckles
03-01-2007, 04:16 PM
I tried to reproduce the error by downloading the page, with prerequesites with wget. However, I can't seem to get the page to render properly when served from my machine. So I can't check directly.

The only possible clue that I have is two images that were downloaded as prerequesites to the episode 11 page that I was using as my test case. I looked at those images in my browser both locally and directly from the indigital page. The one possible clue is that the image
http://www.revision3.com/static/images/arrow_up.png
does not load properly in my browser. When loaded like that, directly, it doesn't crash the browser, but it doesn't show anything.

Sorry I don't have any more useful information.

The image you're referring to is a very small white arrow which might explain why you're not able to see it on your browser.

The individual episode pages loaded fine for me under Firefox on Windows XP, MacOS X, and Ubuntu Linux.

-chuckles-

gevmage
03-01-2007, 05:14 PM
The image you're referring to is a very small white arrow which might explain why you're not able to see it on your browser.

Oh for pete's sake. It's a white arrow. You're right, of course. Argh.

The individual episode pages loaded fine for me under Firefox on Windows XP, MacOS X, and Ubuntu Linux.

Just out of morbid curiosity, what version of Firefox are you using on Ubuntu?

Thanks for your information, Chuckles. I really have no idea what to believe now, other than the only conclusion I can come to is that it's me, but I don't see how.

Well, unless I can come up with something more, or someone else see the same problem, I dont' think there's anything to be done. We now return you to your regurlarly scheduled program of complaining about the inDigital audio levels.

chuckles
03-01-2007, 06:21 PM
Just out of morbid curiosity, what version of Firefox are you using on Ubuntu?


I am using Firefox 2.0 on Ubuntu.

-chuckles-

chuckles
03-02-2007, 11:55 PM
gevmage,

Is your browser still crashing on the individual episode pages?

-chuckles-

gevmage
03-04-2007, 01:49 PM
Is your browser still crashing on the individual episode pages?

Yes, but I don't want to waste any more of anybody else's time until I've nailed it down. I've talked to other people who also run Firefox, and none of them have that problem. So at this point the only single cause scenario is that there's an energy field in my house that makes browsers run pathologically...which would explain some things, actually.

What I need to do is very carefully check versions. Chuckles, you said that you were using Firefox "2.0". Does that mean 2.0.0.0, or what? I have Iceweasel 2.0.0.1, and it exhibits the problem. A friend of mine who runs Firefox under Windows has 2.0.0.2, and it works fine for her. So if I have time today, I'm going to install 2.0.0.2 and some other, slightly earlier version and compare them to 2.0.0.1 on the same machine, and see if I can get some traction that way.