279370 - Crash if the quicktime video goes from buffer mode to play mode sometimes.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[elgogo]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In the page at http://www.matthew-good.com/Program/TWS/TWS_Videos.htm it
sometimes crashes when it tries to load a video.  It could be because it's
literally trying to convert a DNS address into an I.P. address, or it could be
just that Quicktime screws up from buffer mode into play mode.  Or maybe it's
the pop-up window with a plugin inside that's causing it.  (???)  Happens not on
the first try, but after watching 3-5 different videos.  Could be pop-up window
related.

Reproducible: Sometimes

Steps to Reproduce:
1. Play different videos.
2.  Close the pop-up window down when it's not finishing downloading but still
playing the video.
3.  Try to reopen same video.
4.  Quicktime never keeps a cache of the *.mov you partially downloaded before
Actual Results:  
Firefox closed and generated an error.  Unfortunately, I didn't click on details
to find out.  So, I uninstalled and reinstalled Firefox and included the Quality
Feedback agent so if it happens again, I'm prepared.

Expected Results:  
The quicktime plugin shouldn't have crashed firefox.  I believe plugins should
be totally independant of the browser's kernel for there is no interaction
between the browser's kernel and the plugin.  So, if the plugin crashes, it
shouldn't crash the entire browser, only the component.  An analogy:  a car
stereo crashing should not stop the car engine just because the car stereo is
built in the car.

Please make future plugins of firefox independent of the browser's kernel. 
Plugins should never crash the entire browser.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.