197951 - Mozilla using wrong images from cache

Status: VERIFIED DUPLICATE of bug 140530

(SeaMonkey :: General, defect)

Description

[Charles N. Burns]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

Mozilla appears to randomely use the wrong images from its cache, but that
theory could be wrong. In any case, images on certain websites appear to be
randomely swapped with other images. The URL provided shows an example of a
PHPbb forum in which the "Post new topic" image has replaced the little paper
image and been scrunched to fit in the same area as the image it replaced, and
two strange Google glitches.
Which images get replaced seems to be random--I can refresh and different images
will be incorrect, previously incorrect ones will work again.
A similar problem appears on the Google Image search as well. For example, I did
a search for "foo" and clicked on an image that looked like a photo of a text
terminal. Mozilla then displayed an image of a varnished wooden lion, but worse,
it didn't display the full webpage it normally displays with a shrunk image and
some text on the top frame, the source website on the bottom--it JUST displayed
the [wrong] image. The image seems to be from cache since that same image was
elsewhere in the search. This happens 95% of the time on some days, 5% on others.
Some websites seem uneffected. Alltheweb.com, for example, would not exhibit
this behavior, but it could have been random luck.
This does not happen in IE5.5.
In case this is a hardware glitch, I use a Gainward Geforce 3 with the most
recent (December 2002) drivers.

Reproducible: Sometimes

Steps to Reproduce:
1. (unknown) Try: Visit a webpage with many images.
2.  ???
3.  Profit!!!

Actual Results:  
Random image scrambling

Expected Results:  
Displayed the images that the website told it to display.

Comment 1

[Michael Lefevre]

reporter - do you have pipelining enabled?

if so, this is probably bug 140530

Comment 2

[Charles N. Burns]

Correct, that sounds like the same bug. I guess I'm not particularly effective
at searching.

*** This bug has been marked as a duplicate of 140530 ***

Comment 3

[Michael Lefevre]

thanks for the followup.

verifying.