79230 - crash visiting this url.

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect)

Description

[Len Trigg]

When visiting this url from the containing page
(http://www.vh.org/Providers/Textbooks/ElectricAirway/Text/CroupSyndromes.html),
the open/save dialog appears and then mozilla crashes. Mozilla crashes directly
when started from the command line with the problem url -- no dialogs even appear.


I'm using Linux build 2001050711.

Comment 1

[Asa Dotzler [:asa]]

this link does not crash me on win32 or mac (don't have a working linux build
today).  The link opens the default audio player which for me was the windows
media player on win32 and realplayer on Mac. It played a horrible sound but did
not crash.  I suspect a plugin problem for linux but can't back that up yet.

Comment 2

[jorge o. castro]

sort of wfm linux 2001050521. Page loads up fine, nothing happens, no media
player of any kind or plugin request. Page does not crash though. 

Comment 3

[Asa Dotzler [:asa]]

I still don't have a working linux build but from the comments and my testing I
think this is an issue will linux and plugins.  If you don't an appropriate
plugin nothing bad happens.  If you do have a plugin that gets called you crash.
 (this is just a guess)

Comment 4

[shrirang khanzode]

reassigning. Another helper app download dialog crash issue.

Comment 5

[sairuh (rarely reading bugmail)]

there was a problem with earlier builds crashing when bringing up that dialog.
more recent builds don't exhibit this problem --wfm using 2001.05.09.14 mozilla
linux bits.

Comment 6

[sairuh (rarely reading bugmail)]

mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]

b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)