226616 - when I entrt the given URL, mozilla 1.5 crashes, first happend on xmms.org download page

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[klaus thorn]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

on http://xmms.org/download.php a klick on XMMS for Redhat 9.x: XMMS 1.2.8: http
makes mozilla 1.5 crash. entering the URL without being on that webpage gives
same result. no other symptoms whatsoever, really. The source code on the
webpage is okey: <a href="/files/1.2.x/rpm/rh9.x/xmms-1.2.8-1.i386.rpm">http</a>

Reproducible: Always

Steps to Reproduce:
1.enter URL in mozilla 1.5 adress field: 
http://xmms.org/files/1.2.x/rpm/rh9.x/xmms-1.2.8-1.i386.rpm
2.
3.

Actual Results:  
whole mozilla browser window disappeared

Expected Results:  
download an red hat rpm file

I'm experiencing this with red hat 8.0 and 9.0 with above given mozilla version.

<warning>I GUESS</warning> it has to do with mozilla assuming the server of the
URL to be acting correctly, which it may not do.

<unix command line tool>wget</unix> is downloading the URL without problems.
Although with MIME type: audio/x-pn-realaudio-plugin

Until I got here I almost forgot what I wanted to report because of all your
guidelines and help and warnings. Better make ONE good reporting page with
guidance annotations instead. This reporting page is quite good, a few warnings
more will obsolete all the rest, in my humble opinion.

Comment 1

[Boris Zbarsky [:bzbarsky]]

> <warning>I GUESS</warning> it has to do with mozilla assuming the server of the
> URL to be acting correctly

We do.  Anything else would be a bug on our part.

Do you have a plugin for handling audio/x-pn-realaudio-plugin data? And does
this plugin fail to deal with the RPM file here and crash?

Comment 2

[Jesiah S]

I see it to on LInux 2003120506.  When I remove the Real plugin It works fine.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Sounds like a bug in the realplayer plugin itself... nothing we can do about that.