Bug 28626
| Summary: | WebKit quits (no crash log) when a link to a MPEG-1 file is clicked on. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Pook <pook52mb> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | UNCONFIRMED | ||
| Severity: | Normal | CC: | ap |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://www.linux-video.net/Samples/Mpeg1/baby.mpg | ||
Michael Pook
Problem does NOT occur on the same system (G4 1.0GHz, OS X 10.4.11, QuickTime 7.4.5) with Opera 10.0b3, Seamonkey 2.0b1, Camino 2.0b3, Firefox 3.5.2, OmniWeb 5.10 sneakypeek 622.8.0.116947, Multi-Safari 2.0.4, or Multi-Safari 3.0.4 It does however occur with iCab 4.6.1, Safari 4.0.3, WebKit-SVN-r47546.
Check out the files at http://www.linux-video.net/Samples/Mpeg1/ . When the QuickTime Plugin.plugin and QuickTime Plugin.webplugin files are moved to the Disabled Plug-Ins folder within the /Library/Internet Plug-Ins folder, any .mpg files clicked on are downloaded and can then be viewed with QuickTime Player. However, when the QuickTime Plugin.plugin and QuickTime Plugin.webplugin files are moved back to the /Library/Internet Plug-Ins folder, any .mpg files that are clicked on cause iCab 4.6.1, Safari 4.0.3, WebKit-SVN-r47546 to quit immediately, without generating a crash log.
Either MPEG-1 files are not very common on the Web, or I am one of the first to notice this bug.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
I cannot reproduce this with a local debug build of r47661 on Mac OS X 10.5.8 (Intel). Will upgrading to QuickTime 7.6.2 solve the problem for you?
Michael Pook
(In reply to comment #1)
> I cannot reproduce this with a local debug build of r47661 on Mac OS X 10.5.8
> (Intel). Will upgrading to QuickTime 7.6.2 solve the problem for you?
The version of QuickTime is NOT the issue, as both Presto and Gecko based browsers
behave normally. I have removed the newer WebKit 530.20 based versions and replaced
them with older WebKit 530.19 based versions. These older versions also behave normally.
Clearly this issue is with WebKit based browsers using version 530.20 or higher. Perhaps
the issue only affects systems running 10.4.11 Tiger (perhaps only on PowerPC machines)?
I have verified that this is a problem on my eMac M8950LL/A, my iBook M9848LL/A and
on my Mac Mini M9971LL/B. All the above are configured with the same OS and software.
I do not own any Intel hardware or 10.5.8 Leopard to verify the issue on.
Alexey Proskuryakov
The behavior of other browsers is not really important here - they use a different QuickTime plug-in, and they use fewer features of QuickTime.
It is quite possible that WebKit relies on something that only works correctly in newer versions of QuickTime. There is no reason to spend any effort on trying to support old QuickTime versions - one thing we could do is fail to launch if modern QuickTime is not installed, displaying an error message.