130683 - File I/O service uses mime types service on the wrong thread

Status: VERIFIED DUPLICATE of bug 127918

(Core :: Networking: File, defect)

Description

[Scott MacGregor]

I just tried clicking on a local file which required the mime type service. I
noticed a bunch of thread safety assertions. It looks like:
nsFileIO::Open

is getting the nsIMimeService to figure out the mime type of the local file.
It's accessing this service on the file transport thread. Unfortunately the mime
service is not thread safe. It uses RDF to store user specified mime
information. So I'm getting thread safety assertions in the parser when we try
to load the rdf file for the datasource in addition to thread safety assertions
in some I18N charset detection code which is brought in by RDF as well. 

We need to create a proxy on the file transport thread for the mime service.

Comment 1

[Scott MacGregor]

nominating for nsbeta1 since accessing objects on the wrong thread can do bad
things. 

For a test case: create a local html page which has a link to a local MP3 on it.
Click on that MP3 link. Noticed the subsequent thread safety assertions.

Comment 2

[Doug Turner (:dougt)]

I just checked in a fix for this last night on the trunk.  Can you take a look
at this and see if it fixes what you are seeing? 127918

Comment 3

[Doug Turner (:dougt)]

dup

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

Comment 4

[benc]

mscott: can you verify this is a dupe?

Comment 5

[Scott MacGregor]

verified