222666 - Image manager confused by dynamic profile switches

Status: RESOLVED INCOMPLETE

(Core :: Graphics: Image Blocking, defect)

Description

[Thomas Carrié]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

In b.html there are 3 img tags that points to the same moz.gif image using 3
different kinds of URL :
- img src="moz.gif"
- img src="http://localhost:8080/moz.gif"
- img src="http://www.mozilla.org/frontpage/header.gif"
the first 2 img instances are displayed as a blank area, they should be
displayed as the third one

Reproducible: Always

Steps to Reproduce:
tar xfj BugMozilla.tar.bz2
setup a web server on port 8080
mozilla b.html
Actual Results:  
see 2 blank areas

Expected Results:  
see the first 2 images

- my web server is an apache 1.3
- these img are correctly displayed in any other browser : opera, netscape4.7,
mozilla 1.3 (see the screenshot)
- the img is displayed correctly indivually (see the screen shot)
- there is no such bug when I see b.html from other webserver on default port :
http://irilog.com/mozilla/b.html and http://localhost/b.html
- the mime type is correct
   thocar@linux:~> wget http://localhost:8080/moz.gif
   --20:38:20--  http://localhost:8080/moz.gif
             => `moz.gif'
   Résolution de localhost... complété.
   Connexion vers localhost[127.0.0.1]:8080...connecté.
   requête HTTP transmise, en attente de la réponse...200 OK
   Longueur: 5,016 [image/gif]

   100%[=====================================================>] 5,016        
4.78M/s    ETA 00:00

20:38:20 (4.78 MB/s) - `moz.gif' sauvegardé [5016/5016]

It's very hard to tell where the bug comes from :

- if it was an apache bug it would fail on other web browsers (including
moz1.3), it wouldn't work also on http://localhost (same apache, different
virtual host)

- if it was an XHTML bug it would fail both on irilog.com and localhost:8080

- it's not a bug in the gif because it is properly displayed depending on the url

- it's not a bug on the mime type (see wget)

Comment 1

[Thomas Carrié]

Attachment: tar ball of b.html, moz.gif and screen shots

Comment 2

[Boris Zbarsky [:bzbarsky]]

Any chance of making public a url where the problem can be reproduced?  I just
tried this locally here and it works fine...

Also, does clearing your cache help? You may have something cached for that
image URL that doesn't contain valid image data...

Comment 3

[Thomas Carrié]

I have cleared the cache, changed the cache location, the cache strategy it
doesn't help.

But I have switch profiled, it works well on any other profile, it works well
also with any other user of the same machine.

So the conclusion is that my profile is somehow corrupted, it is very tricky bug
because it works with the same profile using mozilla 1.3.

But how do my profile got corrupted in such a tricky way that I cannot repair it
easily and that it affects permanently such a basic feature.

I think I will recreate my profile from scratch, but I'm little bit scared that
it will get messy again because I was doing some regular HTML editing on my web
pages when I wondered why a particular image could not be displayed, then I
realized that any other images of the same site (localhost:8080) could not be
displayed as well.

Thanks a lot for help you gave me.

The bug must be somewhere in the data associated with my profile for the site
localhost:8080, I don't know how to help more, feel free to close the bug except
if you think there are some things I can futher investigate.

Comment 4

[Thomas Carrié]

there is no image blocking configured in my profile for any web site

Comment 5

[Boris Zbarsky [:bzbarsky]]

If you could attach your prefs.js, that would be great.

Comment 6

[Thomas Carrié]

Attachment: Mozilla preference file of the corrupted profile

Comment 7

[Boris Zbarsky [:bzbarsky]]

Could you also attach your cookperm.txt file?

Comment 8

[Thomas Carrié]

Attachment: cookperm.txt

cookperm.txt

Comment 9

[Boris Zbarsky [:bzbarsky]]

That cookperm.txt has the line:

  localhost:8080	1F

That means "loading allowed from 'localhost:8080' == FALSE"

That doesn't match up with comment 4...  Is the UI not showing things right?

Comment 10

[Michiel van Leeuwen (email: mvl+moz@)]

With the attached cookperm.txt, i see two entries in tools->image
manager->manage image permissions.
Thomas, you say that manager is empty for you? that is kind of weird. I can't
really think of anything that might cause that to happen.

Comment 11

[Thomas Carrié]

We are getting closer : there must be a bug in the "image blocking" managment

I start moz under profile t2 (my new profile)
I switch to profile thocar (my old corrupted one)
I quit moz
I start moz
I look at Tools/Image Manager/Manage Image Permissions
    I see 2 blocked site including localhost:8080
I look at Preference/Privacy/Image/Manage Image Permissions
    I see 2 blocked site including localhost:8080
I switch to my new profile t2
I switch to my profile thocar
I look at Preference/Privacy/Image/Manage Image Permissions
    I see no blocked site
I look at Preference/Privacy/Image/Manage Image Permissions
    I see no blocked site
I quit moz
I start moz
I look at Tools/Image Manager/Manage Image Permissions
    I see 2 blocked site including localhost:8080

Comment 12

[Boris Zbarsky [:bzbarsky]]

Sounds like the image manager needs to handle dynamic profile switches better...

Comment 13

[Alin Ilea, Desktop Test Engineering]

Marking this as Resolved > Incomplete since the last activity on this issue was 12 years ago and it might not be relevant anymore. Feel free to re-open if the issue is still reproducible on your end in the latest FF versions.