186109 - random crashes in Gentoo/Gnome

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Tom Whipple]

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

Mozilla crashes after a random interval of proper behavior. I can't seem to pin
down a cause, though it seems to happen sooner if I am doing several things at
once, like muliple windows/tabs or browsing and reading mail.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Use browser and/or mail for a while.
2. It crashes.
Actual Results:  
All windows disappear.

Expected Results:  
Continued normal operation.

I can't seem to find any crash data. There is no core file. If I fired it from
the console, there is no output to STDOUT. I am running Gentoo, Gnome/enligtenment.

Is there a switch or environment variable I can turn on to enable debug output
of some type?

Comment 1

[Tom Whipple]

Ok, I can now reproduce it 100% of the time.

1. Go to http://www.worldlanguage.com/Products/8428.htm
2. Click "Add to Cart"
3. Click "Check Out"

Mozilla dies as soon as I touch the "Check out" button. It doesn't seem to wait
untill the next page loads. (The check out button does happen to be a post to an
HTTPS url, while the page I am looking at is not encrypted.)

However, it should be noted that there are other random moments where the
browser just seems to crash for no apperent reason or connection to anything.

Comment 2

[Matthias Versen [:Matti]]

wfm with a 1 day old cvs trunk on win2k

Comment 3

[Tom Whipple]

It also works in 1.2.1 on Win2k, and is quite stable for me on that platform.

Comment 4

[Tom Whipple]

Ok, here's another crash scenario: ( 100% reproduceable ).

1. Open mozilla. (In this case after previous crash.) 
2. Click mail icon at bottom of browser window. 
3. Log in to IMAP when prompted for password.
4. Click compose.

The compose window doesn't quite finish drawing, when BOOM, it's gone. Maybe it
will work after doing other stuff first? 

Comment 5

[Tom Whipple]

Nope. Same behavior after I look at a few messages, then hit compose. Ditto if I
log in and hit reply.

I would say that my average Mozilla uptime during active navigation is 5-20 min.

I might have to fall back to windoze for a while. AHHH. Wait, there's pine. ;-)

Comment 6

[Andrew Schultz]

are you using a .mozilla.org build?  If yes, please provide a talkback ID for
one of the crashes.  If not please provide a gdb stacktrace...

Comment 7

[Chris Lyon]

This bug has morphed into a general crash bug.  Please keep it to one crash
scenario per bug report.

->INVALID