405689 - quicktimestreaming.qtx and MSN Web Messenger cause firefox to report "encountered an error and needs to close"

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Kit Peters]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1

When using MSN Web Messenger w/ FF 3.0b1, periodically I get the message from Windows, "firefox.exe has encountered an error and needs to close".  Looking at the data from the error report, I see the "ModName" as quicktimestreaming.qtx.  This likely corresponds to my having installed Quicktime from Apple earlier in the day.

Reproducible: Always

Steps to Reproduce:
1.  Navigate to MSN Web Messenger and sign in
2.  Wait
3.  Error message comes up


Expected Results:  
No error message should have come up.

Error signature:  AppName: firefox.exe AppVer: 0.0.0.0 ModName: quicktimestreaming.qtx ModVer: 7.3.0.70	Offset: 00091cf4

Comment 1

[Matthias Versen [:Matti]]

Please provide a Breakpad ID :
http://kb.mozillazine.org/Breakpad

I will close this bug as invalid If this is really caused by quicktime.

Comment 2

[Kit Peters]

I'm not sure how to find this breakpad ID.  I went to the folder specified in the KB article, and did not find either of the folders the KB article mentions.  I have two files:  "InstallTime2007110904" and "UserID".

Contents of "InstallTime2007110904": "1196092300"
contents of "UserID": "488a77da-9e47-4267-88e7-0cc6d52fe7e8"

Comment 3

[Matthias Versen [:Matti]]

There shoulkd be crash reports of you submitted one but this seems to be a problem with the plugin itself. You may report this to apple.

Comment 4

[Tyler Downer [He/Him]]

Does this still happen with Firefox 3.6.6 or later in a fresh profile?

Comment 5

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.