291523 - crashes if I click on link whose file extension doesn't exist in mime.types

Status: RESOLVED EXPIRED

(Core Graveyard :: File Handling, defect)

Description

[N. Thomas]

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.6) Gecko/20050327 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.6) Gecko/20050327 Firefox/1.0.2

If I click on any link that is for a file which does not have a mime.types
entry, Firfefox crashes on me.

I suspect the problem is with libnullplugin.so, about:plugins says that it is
not enabled.

Reproducible: Always

Steps to Reproduce:
1. click on any link that is for a file without a link in mime.types
2.
3.

Actual Results:  
hangs/crashes. need to kill -9.

Expected Results:  
Asked if I want to open the file it with a program or save to disk

Comment 1

[N. Thomas]

Just FYI: I just upgraded Firefox to 1.0.3 and the problem still exists..

Comment 2

[N. Thomas]

I just enabled the nullplugin plugin and it still crashes 

Comment 3

[N. Thomas]

I did a bit more debugging with ktrace today, and here is some more info on the bug:

1. Firefox crashes whenever I tried to save/download a file from a link whose
extension is not in ~/.mime.types. (I tested this thoroughly)

2. For whatever reason, only ~/.mime.types is looked at,
/usr/local/etc/mime.types  is opened and read, but it is never used. If the
extension is not in ~/.mime.types, then the browser crashes.

Comment 4

[N. Thomas]

I compiled Firefox with debugging and logging enabled, and I was able to get it
to crash again, but not before it spit out the following useful information:

###!!! ASSERTION: Null encoding type: 'aEncodingType', file
nsExternalHelperAppService.cpp, line 618
Break: at file nsExternalHelperAppService.cpp, line 618
spec=/Mozilla
WARNING: malformed url: no scheme, file nsStandardURL.cpp, line 682

Comment 5

[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 6

[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.