522801 - SeaMonkey v1.1.18's Web browser/Navigator crashes ("QuickTime failed to initialize. Error # 0. Please make sure QuickTime is properly installed on this computer...") when using QuickTime v7.6.4.

Status: VERIFIED INVALID

(SeaMonkey :: General, defect, P3)

Description

[Ant]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

Hello.

Ever since I upgraded my QT v7.6.2 to v7.6.4, I have been getting this error with embedded QuickTime MOV on various Web pages (e.g., http://www.specialproblems.com/wolfmother.htm ). The error said "QuickTime failed to initialize. Error # 0. Please make sure QuickTime is properly installed on this computer." Then, another error that said "Illegal operation in Plug-in -- The plug-in performed an illegal operation. You are strongly advised to restart SeaMonkey."

SeaMonkey's about:plugins shows:
QuickTime Plug-in 7.6.4

File name: npqtplugin.dll
The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.

MIME Type Description Suffixes Enabled
application/sdp SDP stream descriptor sdp Yes
application/x-sdp SDP stream descriptor sdp Yes
application/x-rtsp RTSP stream descriptor rtsp,rts Yes
video/quicktime QuickTime Movie mov,qt,mqv Yes
audio/x-wav WAVE audio wav,bwf Yes
audio/wav WAVE audio wav,bwf Yes
audio/aiff AIFF audio aiff,aif,aifc,cdda Yes

This only happens in Mozilla's SeaMonkey (SM) v1.1.18's Web browser in four differrent updated Windows XP Pro. (SP2 and SP3) machines (one was a clean image with new installations of QT and SM). Internet Explorer v6.0 SP3 and Firefox v2.0.0.20 worked fine though. I downgraded QT back to v7.6.2 and no more crashes.

I also tried it again with SM v2.0 RC1, and it had no problems (had to copy QT plugin files over).

I also asked in Mozilla's SM newsgroup ("QuickTime Alternative/Lite v3.0.0 crashes SeaMonkey v1.1.18...") and one reported the same problem in his v1.1.18 with the latest QT. It seems like there is a bug between SM v1.1.18 and QT v7.6.4.

Thank you in advance. :)

Reproducible: Always

Steps to Reproduce:
Reproduced 100% on four different machines with SeaMonkey v1.1.18, updated Windows XP Pro. (SP2 and SP3), and updated Internet Explorer v6.0.

1. Install SeaMonkey (SM) v1.1.18 with defaults.
2. Install Apple's QuickTime (QT) v7.6.4 (http://www.apple.com/quicktime/download/) OR QuickTime Alternative/Lite v3.0.0 (http://www.codecguide.com/ -- uses QT core components without the bloated GUI and stuff) with defaults. Ensure the QT plugins files are installed for SM.
3. Go to a Web site that will use QT like http://www.specialproblems.com/wolfmother.htm ...
Actual Results:  
Two crash errors should appear with "QuickTime failed to initialize. Error # 0. Please make sure QuickTime is properly installed on this computer." Then, another error that said "Illegal operation in Plug-in -- The plug-in performed an illegal operation. You are strongly advised to restart SeaMonkey." OR crashed due to quicktimewebhelper.qtx v7.6.4.0 (didn't record its exact message).

Expected Results:  
Embedded QuickTime MOV should appear without crashing SeaMonkey.

Comment 1

[Matthias Versen [:Matti]]

SM1.X will get only security fixes AFAIK
The error message is from the plugin itself and not from Gecko and the crash is a cause of the plugin malfunction.

Comment 2

[Ant]

Thanks Matthias/matti.

Does anyone know how to report bugs to Apple QuickTime team?? I already posted in its forum, but got no replies so far. :(

Comment 3

[Matthias Versen [:Matti]]

Sorry, I have no idea how to contact them.
QT is a real problem on win32 and that is the reason I uninstalled it this year.
BTW: Using older QT versions is a high security risk.

SM2.0 is coming too late because Gecko1.8.X is already behind it's EOL (FF2.0.X is not supported anymore). The SM people are working hard to get SM2.0 out and I think you will have a final Seamonkey2.0 before you get an answer from apple.

Comment 4

[Ant]

Thanks again. I wonder what is so different in Windows' v1.1.18 for QT plug-ins to crash. Is there a detailed changelog or something?

Comment 5

[Robert Kaiser]

OK, the comments here make it a tie between INVALID (i.e. "not our bug") and WONTFIX (i.e. "we're not actively working on 1.x any more"). I'll resolve it as the former, not being actually our bug but Apple's.

Comment 6

[Matthias Versen [:Matti]]

http://www.mozilla.org/security/known-vulnerabilities/seamonkey11.html#seamonkey1.1.18

Only this 2 security bugs are fixed between 1.1.17 and 1.1.18 and nothing more.

Comment 7

[Jason Bassford]

Per comment 5 this was supposed to be resolved as INVALID - but it's been resolved as FIXED instead.  Was that a mistake?

Comment 8

[Robert Kaiser]

oops, yes, it's INVALID.