Closed Bug 167018 Opened 23 years ago Closed 23 years ago

Some pages doesn't load fully

Categories

(Core :: Networking: HTTP, defect)

x86
FreeBSD
defect
Not set
major

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: telac, Assigned: darin.moz)

Details

After installing from the newest port collection after CVSup on FreeBSD 4.7 Mozilla 1.1 - Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020905 I have a problem loading pages like www.ekstrabladet.dk and www.jp.dk, the pages loads a little graphic and then stalls. The second I enter a new URL the pages loads fully and then mozilla starts refusing looking at other pages and require a restart. It may be due to some java applet or flash on them, but I have neither installed, and with the old version of mozilla, it just displayed a grey field and the "Do you wish to install Java applet?" thingy, but now mozilla stalls totally.
WORKSFORME linux trunk 2002090312 (flash, java not installed). since i do not have a freebsd system to test on, there's unfortunately not much i can do with this bug :(
Reporter: Have you tried clearing the disk cache ? Are you using a proxy ?
I am not sure its a OS dependent problem. I have no other OS' than FBSD around, and thus I cannot check with the same version of mozilla. Tried clearing the disk cache .. no luck. I am not using a proxy, its running from a X terminal server, so all users share the same browser (and user profiles is being a pain in the behind :) It feels like the page www.ekstrabladet.dk doesn't load untill you enter a new url. I only have problems with www.ekstrabladet.dk and www.jp.dk so far .. but they load after a few minutes. Could it be some shockwave/java applet problem?
Severity: critical → major
Worksforme with 2002110708-trunk/FreeBSD 4.6.2.
Works for me on Win2000, Mac OSX and Linux. Reporter, please reopen if you can reproduce with a new build.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
QA Contact: httpqa → junruh
Resolution: --- → WORKSFORME
V
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.