149346 - after install most images came up broken

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[jamie dalgetty]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530
BuildID:    2002053012

after installing mozilla 1.0 web browsing was very difficult because most images
were comming up broken

i tested this against netscape 7.0 rcX and ie and they both worked fine.

restarting windows seems to have solved this problem

Reproducible: Couldn't Reproduce
Steps to Reproduce:
1. install moz 1.0
2. browse any page

Actual Results:  the first time, most images didnt load

Expected Results:  obviously it should have worked

Comment 1

[Matthias Versen [:Matti]]

Reporter: 
Can you please clear the Disk cache ?
Have you installed over an older build ?
Do you run Mozilla and Netscape at the same time with the same profile ? 

this is never XP APPS..

-> b-g

Comment 2

[Colin S]

I have a similar problem. It started recently, I'm not sure what the catalyst
was. From what I can tell, the images run together, for example:

7fe
ÿØÿà JFIF  ` `  ÿÛ C 
[binary data]
0 à0[Ô
49
ˆd) Qõ¢
u±WínË­ø¯0‚¨
‡˜(¹ÔÙŽäÖå¬bEN TWh‡ÝBèë›û|ÂN”«iGüÿÙ
0

HTTP/1.1 200 OK
Date: Mon, 05 Aug 2002 17:48:22 GMT
Server: Apache/1.3.9 (Unix)
Last-Modified: Mon, 01 Feb 1999 02:54:48 GMT
ETag: "55af04-131-36b51778"
Accept-Ranges: b
Transfer-encoding: chunkedytes
Keep-Alive: timeout=5, max=96
Connection: Keep-Alive
Content-Type: image/gif

131
GIF89a    ³     $$$lllÿ3 ŽŽŽ»»»ØØØÿÿÿÿÿÿ
[binary data]
)D  ;
0

The first part is a JPEG/JFIF image, and the second is a GIF image. These,
however, were both in the SAME cache file with the header in between, like this.
(I just removed some of the binary data as it is useless in showing the point.)

Comment 3

[Colin S]

This problem is related to HTTP Pipelining. (Evil.) Go to Preferences > Advanced
> HTTP Networking and uncheck "Enable Pipelining". Ta'da! Problem solved!

Nominating RESOLVED.

Comment 4

[Benjamin Smedberg]

->WFM   jamie: if this problem reoccurs using a new build of mozilla (1.2a) with
your disk cache cleared and HTTP pipelining off, please re-open this bug.  Thank
you!