Closed Bug 135968 Opened 23 years ago Closed 23 years ago

Mozilla crashes with some files without a HTML <head>

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: sryll, Assigned: Matti)

Details

(Keywords: crash)

Attachments

(4 files)

It happened to me to Mozilla crashed with the following message on the command line when I tried to open a file without <head>: -- steffen@steffen:~/mozilla/dist/bin > ./mozilla [did a ^z] [1]+ Stopped ./mozilla steffen@steffen:~/mozilla/dist/bin > bg [1]+ ./mozilla & steffen@steffen:~/mozilla/dist/bin > /home/steffen/mozilla/dist/bin/run-mozilla.sh: Speicherzugriffsfehler $prog ${1+"$@"} -- It were two files from the Mplayer package (www.mplayerhq.hu) in the DOCS directory: documentation.html and codecs.html. The crash was no reproduceable and happened only once with each file. When I looked at them, I noticed only, that there was no "!DOCTYPE"... and the document started with <html><body>, i.e. no <head> item.
which Build ID ? Do you have a talkback ID for that crash ?
Severity: major → critical
Keywords: crash
It is a build from CVS, pulled on 31/3/2002. I have never seen talkback on Linux yet :-(
I just did a quick test with a very simple test file (<html><body></body></html>) and I didn't see any problems with build 20020406 under Win98SE.
The <head> tag is optional. Things like <title> <meta> and <style> tags that generally go in the <head> don't even have to. The !DOCTYPE is also optional. Talkback is included with some of the precompiled binary builds.
This is one of the mentioned files. As I stated already, Mozilla doesn't crash always, but it happened three times altogether now. What I did: 0. I was offline (no dial-up connection) 1. I started mozilla: $ cd mozilla/dist/bin $ ./mozilla 2. I opened the file via File-> Open File and picked MPlayer-0.60/DOCS/codecs.html (the one I appended) 3. _Sometimes_ Mozilla crashed with a SEGFAULT (I posted the message already)
(how often is "sometimes"?) worksforme with linux build 20020405. could you provide a stacktrace (via gdb)? without that or talkback info, it's going to be hard to tell what's wrong. what were your build options?
I (tried to) produce(d) a stack trace with gdb. This is what happened. My build options were ./configure --disable-mailnews --enable-java-supplement --with-ldap --with-gnu-ld --enable-reorder --enable-strip --enable-mathml --disable-debug --disable-tests --enable-crypto
I also made an "strace -fF -o strace-mozilla ./mozilla" to provide more information. BTW, the Bug Writing Guidelines say, I should call "gdb mozilla core". But how do I create the "core" file. You see, I'm not very experienced with gdb & Co. ... Ahh, and you asked for the "how often": This crash is not really reproduceable. It occurs about every fourth or fifth start. I cannot see any conditions, under which it occurs and under which not. :-( I have still a gdb session with a crashed mozilla open (./mozilla -g) (now means 2002/04/07 18:25 MEST). If you would like to find out more, let me know.
Do you still have that gdb session? Could you see what the stacks are for the various threads? thread 1 bt thread 2 bt and so on till you run out of threads? Also, on Linux the kernel does not create core files of multithreaded programs (yay kernel bugs).
I didn't have that session any longer... Sorry, my computer stands next to bed... However, I did what you told me and now append a stack trace of all threads. Do I understand right: (Under Linux,) there are no core files for mozilla?
> Do I understand right: (Under Linux,) there are no core files for mozilla? Barring possible kernel changes in the 2.4/2.5 series, yes.
I made some experiments with RC1 (#2002041711 Linux). After maybe 20 tries, Mozilla hasn't crashed once, so seems to be worksforme as well. A few minutes ago, I pulled the most recent source and will check out how my own build behaves.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: