141826 - mail attachment with mime application/x-java-vm crashes

Status: VERIFIED WORKSFORME

(MailNews Core :: MIME, defect)

Description

[llanero]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417
BuildID:    2002041711

Double clicking on an attachment cause mozilla to crash. I have RC1 with talback
and the talback window does not show.

Reproducible: Always
Steps to Reproduce:
1. select the mail message
2. double click the attachment
3 [details] [diff] [review]. mozilla crashes
4. NO TALKBACK window

Actual Results:  mozilla crashes.
no talback window.

Expected Results:  mozilla not crashing and showing the attachment (ask for
save/open).
talback showing it mozilla crashes.

Comment 1

[llanero]

how should I attach the message?

should I send the message to some address?

Comment 2

[Jean-Francois Ducarroz]

Please attach the whole message that cause the crash to this bug report if it's
ok for you else, you can forward the message AS INLINE directly to me
(mailto:[e-mail]).

To attach the message to this bug report, select the message in the mail3Pane
window and select menu File/Save As/File and then clik on the Create a New
Attachment link above.

Thanks

Comment 3

[llanero]

Attachment: the message that causes the crash when double-clicking the attachment

Please, tell me if you can reproduce it.

Comment 4

[Andrew Schultz]

I see the same with linux build 20020501.

If I save the file and open it with that mime type, it dies with the following
error:
INTERNAL ERROR on Browser End: [0] Initialize. No docbase?
System error?:: Resource temporarily unavailable

marking NEW
==> OJI?

Comment 5

[Andrew Schultz]

Attachment: mail attachment

Comment 6

[Jean-Francois Ducarroz]

Seth, can you take a look at this problem and see if you can reproduce it?

Comment 7

[Stefan A. Möller]

I have the same problem with linux build 2002052309.
It's always reproducable if you attach a plain text file that has no extension.
No need to actually send the message, just leave it in your "unsent messages"
folder and try to open the attachment. See the following examples:
(a) message with plain text file attached, named "textfile.txt" -> works fine
(b) message with exactly the same text file attached, now named "textfile" ->
mozilla crashes when double-clicking the attachment (note that mozilla is
choosing application/x-java-vm as the mime type for the attached text file)

Comment 8

[Stefan A. Möller]

Attachment: example (a) message with "textfile.txt" attached -> works fine

Comment 9

[Stefan A. Möller]

Attachment: example (b) message with "textfile" attached -> crash

Comment 10

[Andrew Schultz]

*** Bug 151446 has been marked as a duplicate of this bug. ***

Comment 11

[esnible]

*** Bug 152020 has been marked as a duplicate of this bug. ***

Comment 12

[esnible]

I found I can crash the browser by surfing valid Java .class files if the server
gives them the mime type of application/x-java-vm (usually .class files are
considered application/octet-stream).  Example to crash Mozilla: click on
http://www.snible.org/java/Water.class

I've reproduced this on Linux with both JDK 1.3.1 and 1.4.

I can reproduce it in MailNews if I go into Mozilla
Preferences->Navigator->HelperApplications and give .class files the MIME type
of application/x-java-vm, send myself email with a valid Java .class file as an
attachment, then double-click on the attachment.

Comment 13

[Peter Lubczynski]

I don't have a linux machine handy now, but could this be a general problem with
trying to use Java as a full-page plugin? I thought I've seen another bug like
that. Does opening attachment 82151 [details] directly in the browser crash? It WFM on
Win32 w/1.4.

Comment 14

[Andrew Schultz]

Peter: the crash is probably a linux-only problem.  there are really two bugs.
1. filenames without an extension are assigned mime-type application/x-java-vm
2. OJI plugin crashes (exits) on invalid applet (a file mis-identified as an 
   applet).

#1 might be platform-independent, but #2 is probably not (if you don't crash on
attachment 82151 [details])

Comment 15

[Andrew Schultz]

*** Bug 152587 has been marked as a duplicate of this bug. ***

Comment 16

[Joe Chou]

I happened to run into this problem today.I double clicked on an attachment (a
plain text file without any suffix, i.e., "attachment1 [details] [diff] [review]") in one of my mail, the
browser exited with -1 (no crash), and with some error message, saying "error on
browser end. No docbase". (the error was from java plugin) This happened on
Linux and Solaris, moz094 through moz1.1a+. 
After some testing, the problem seems to be the way the file type of an
attachment without suffix being translated. Currently, if Java plugin is loaded,
in "About Plugins" you will see Java mimetypes are the only ones that have no
suffixes. Somehow, the attachments without suffixes then are translated as Java
files (with "application/x-jvm..." ect.).Then when you try to open the
attachment, (the "java" file), which actually can be a plain text file, JVM is
invoked to try to read the file, and returns an error to the browser, which
caused the browser to exit with -1.
On the other hand, if you take out java plugin (removing symbolic link in
"plugins", etc.), then when you double click on the no-suffix attachment, the
attachment will be treated as an unkown file type, and a popup window will
prompt you to either save the file or open it with your choice of file type.
That seems to be the right way to handle an attachment without file type suffix.
The problem of treating mail attachments without suffixes as Java files has been
there since ns4.7x. But in ns4.7x, even though it shows you that such attchments
are jave mime type, when you try to open it, a popup window comes up asking you
to either save it or open it as a file type of your choice.

I think an attachment without any suffix should be treated as file type unknown,
not as java. So that the user can either choose to save it or open it with a
file type of his/her choice. 

Comment 17

[Joe Chou]

This problem could be more serious on Unix (Linux, Solaris, etc.) than on
Windows, since text files usually do not have suffixes. As what happened to me
today, Unix people are likely to attach such files in their mail.

Comment 18

[Joe Chou]

This also happened on Windows XP, moz1.0, JRE 1.4.1. When I tried to open the
no-suffix attachment by double clicking on the attachment, except the mail
contents portion got darken, nothing happened (no pupup window, etc.), but the
browser did not exit either. But when I closed the mail window, a Java exception
pupup window came up, with error of "unknown source". 

Comment 19

[Joe Chou]

Changed platform to all.

Comment 20

[esnible]

There are two bugs here.  First, an incorrect MIME type is being given to files
without extensions.  Second, if an email arrives with the MIME type of
application/x-java-vm then clicking on the attachment kills Mozilla.  I regard
the second problem as more serious.

Comment 21

[Andrew Schultz]

*** Bug 158134 has been marked as a duplicate of this bug. ***

Comment 22

[Andrew Schultz]

*** Bug 161291 has been marked as a duplicate of this bug. ***

Comment 23

[Shanmugavelu Shanmuganathan (gone)]

I see this problem with mozilla1.0. But I couldn't recreate this problem with
the later versions of Mozilla (Mozilla 1.1 alpha and beta). I also tried with
the trunk builds and it seems to have fixed somehow. Anybody else see this problem
still with the newer builds?

Comment 24

[Andrew Schultz]

still crashing here with linux trunk build 20020813.  do you crash if you load
attachment 82151 [details] in the browser?

Comment 25

[Mitch]

Still crashes on build 20020815 on Solaris using my example from Bug 161291.

Note: this is not Linux specific and should be removed from the  "Summary"
statement.

Comment 26

[Shanmugavelu Shanmuganathan (gone)]

My mistake (comment# 23). I didn't have the Javaplugin file in plugins directory.
When I linked the javaplugin140.so, I did see the problem. Sorry.

Comment 27

[Yuedong Du]

See also bug 153930

Comment 28

[Andrew Schultz]

*** Bug 166109 has been marked as a duplicate of this bug. ***

Comment 29

[John Malmberg]

An underlying problem for this bug is that Mozilla is not protecting itself from
errors in the plugin code.

If a plugin gets a fatal error, instead of Mozilla just terminating the
execution of the plugin routine and giving a diagnostic, the entire Mozilla
application crashes.

This is a problem for both the browser and for the mail/news client.  The recent
ability to disable plugins for the mail news client makes this less of an issue
for the mail client but the root problem is common to the web browser and to the
mail and news client.

Comment 30

[Michael Marxmeier]

*** Bug 181457 has been marked as a duplicate of this bug. ***

Comment 31

[Andrei Solodin]

*** Bug 188637 has been marked as a duplicate of this bug. ***

Comment 32

[sairuh (rarely reading bugmail)]

*** Bug 262131 has been marked as a duplicate of this bug. ***

Comment 33

[Asa Dotzler [:asa]]

transferring blocking flag from dupe.

Comment 34

[Andrew Schultz]

sariuh: what JRE are you testing with?  This bug (141826) has been "fixed" since
at least Sun JRE 1.4.2 (and maybe earlier 1.4.x versions).  1.5.0 also works ok.
 It was also avoided by fixing bug 153930, but even without that Mozilla should
hand the attachment off to the JRE plugin, which says "that's not a java
applet!" and everyone goes on about their business (without crashing).

And in bug 262131, why was the plugin getting triggered anyway?  That just
sounds completely wrong (and not related to this bug)

Comment 35

[sairuh (rarely reading bugmail)]

I've got JRE 1.4.2_05 installed.

Comment 36

[chris hofmann]

getting down to the wire on 1.0.  if a patch appears for this one renominate.

thanks

Comment 37

[Asa Dotzler [:asa]]

if this is fixed in 1.5, we're not likely to spend cycles on this for Firefox 1.0.

Comment 38

[sairuh (rarely reading bugmail)]

after a bit of searching, it looks like JVM1.4.2 is the latest version for Linux
and Mac OS X. not sure when those will be updated...

Comment 39

[Calum Mackay]

The official release of J2SE 5.0 (aka 1.5.0) is available for Solaris SPARC &
x86, Linux x86 & AMD64, and Widnerz.

http://java.sun.com/j2se/1.5.0/

Comment 40

[sairuh (rarely reading bugmail)]

Calum, thanks for the link!

after installing jvm1.5.0, I no longer experience the crash. should this be
marked w4m since there's now a workaround?

Comment 41

[Andrew Schultz]

sariuh: in bug 262131, did you have the 1.4.2 plugin symlinked properly in the
plugins directory (did loading the java console work)?  Beyond that, the steps
you described should not trigger the plugin at all (regardless of whether it
crashes or not).

Anyway, this particular bug is WFM

Comment 42

[sairuh (rarely reading bugmail)]

nod, vrfy'd as w4m nowadays.