59383 - Crash on CVS build from 11/6/2000

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect, P3)

Description

[Scott Gifford (old account)]

During a several-hour session of normal browsing, Mozilla managed to crash on me.

In the past, I have used talkback builds, and would report crashes that way.
Now that I'm building from CVS, I'm not sure what the best way to report is, so
I'm doing it this way.  Please let me know if there is something better I should
do.  Also, Mozilla doesn't seem to be producing coredumps when it dies.  Is
there something I can use to enable that?

After several hours of heavy use, Mozilla suddenly shut down on me, with bash
reporting an exit status of 139.  This is with a CVS build from 11/6/2000, on a
PC/Linux system.

I ran Mozilla sending its stdout and stderr to a file; I have attached that file
here.

I have noticed this problem for the last several builds; no specific link seems
to trigger it, just after using it for a while, it will die.

I went to an SSL site during my session, and although I was not there when the
crash happened, I had noticed that psm was still running.

Please let me know what I can do to make crash reports more useful.

Comment 1

[Andreas Franke (gone)]

The most valueable information in bug reports are the steps to reproduce.
Since you are running on Linux and building yourself, you could enhance the bug
reports with stack trace information, but the steps to reproduce are much more
important. You could try running mozilla within gdb all the time, and when a
crash occurs, you can get the stack trace with the bt (=backtrace) command in
gdb. If you are building without --disable-debug, you get even better
information with the "where full" command.

See http://www.mozilla.org/unix/debugging-faq.html for details.
Note: As mentioned there, it may be necessary to get a post-5.0 version of gdb.
Let me know if you need further info.

Comment 2

[Scott Gifford (old account)]

I was unable to attach for some reason.  The file is available at:

http://www.tir.com/~sgifford/mozilla.crash.out

It is the console output of Mozilla before and during the crash.

Comment 3

[Asa Dotzler [:asa]]

Scott Gifford, are you seeing these same crashes on the nightly builds? Can you
try one of the Installer nightlies(doing a complete install installs talkback
for the build).

Comment 4

[Scott Gifford (old account)]

I'm downloading a nightly installer as we speak.  I just had another crash, after about 4 hours of hard browsing.

Comment 5

[Scott Gifford (old account)]

Whoops...Sorry for the big block of incorrect status changes.  I entered my last
set of comments in a beta version of a different browser, and I guess it did
something wrong.  :)

I've changed them all back.

Comment 6

[Keyser Sose]

Reporter is this still a problem in the latest nightlies?

Comment 7

[Boris Zbarsky [:bzbarsky]]

Likely a duplicate of bug 59930

Comment 8

[Asa Dotzler [:asa]]

121308 mozilla linux builds working for me.