448806 - SM still crashes at random

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[mhr]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11

Every once in a while, Seamonkey just crashes without any particular warning.  It seems to occur:

1) After SM has been running for a long time (> 24 hours)
2) When accessing a link (doesn't seem to matter what kind or which one or
3) When accessing internal operations (e.g., bookmark managing).

This has happened to me twice when clicking on a link from my email to a Yahoo Groups moderation page (I moderate lots of Yahoo Groups), but this last time, a few minutes ago, it happened when I was managing my bookmarks, I had opened two folders, and I click on a bookmark to move it from one folder to the other.  As soon as I clisked on the link, SM crashed.

I have come to expect this behavior, though with more regularity, running 1.1.11 on a 64-bit machine, esp. when trying to save a page to a file (set), but now this is even happening on my work desktop (32-bit machine).


Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. No idea.
2.
3.
Actual Results:  
Crash

Expected Results:  
No crash

Comment 1

[Tony Mechelynck [:tonymec]]

Might this be related to bug 445540?

Comment 2

[mhr]

Actually, yes, it is.  I did a search before filing this one and for some reason that one did not show up.

However, 445540 was (IIRC) specifically directed at running SM 1.1.11, 32-bit on a 64-bit platform.  This one is directed to 32-bit platforms (same SM).

If that is (or turns out to be) the same problem, so be it.

Thanks!

mhr

Comment 3

[Tony Mechelynck [:tonymec]]

No prob. Me too, I rarely find the bug I need when doing a search. It's just that I'd recently got bugmail for that other bug so I remembered it. :-)

Comment 4

[mhr]

More information:  it just happened again, this time when I tried to open my spam email folder in Gmail, and I hadn't been running SM for more than about four hours, so the time factor might not be as important as I thought.  (32-bit on 32-bit OS/CPU)

HTH

mhr

Comment 5

[mhr]

More information:

I seem to have less trouble with SM 1.1.11 on my 64-bit platform - it almost always crashes when I try to save a web page (File->Save As), although once in a while it does not.  Yesterday, I was doing a fair amount of bill paying, and I'd forgotten to use my 64-bit build (which almost never crashes, but won't run the adobe reader plugin or the adobe flash plugin), so I saved a screenshot of the first page I wanted to save, and it also saved the page.  This happened about five or six times in a row, which is extraordinary - it usually crashes on the first save attempt.

However, my 32-bit machine at work crashes at least once a day, usually on a click to do something.  Just now it crashed when I tried to switch tabs (and this is the second time that has happened).  So now that makes three incidents that often, though not always, relate to crashes.

Hope that helps - this is one seriously annoying problem.

Thanks!

mhr

Comment 6

[mhr]

I have stepped back to SM 1.1.10 on both work (32-bit) and home (64-bit) desktops, and the level of stability is significantly higher.  Makes me wonder if there was some fundamental change between 1.1.10 and 1.1.11 that introduced this instability.

HTH.

mhr

Comment 7

[mhr]

Well, although 1.1.10 seems to be slightly more stable, I now have a new machine at work, a core2duo based machine, and so far, SM has crashed so many times I have lost count.  It has crashed during startup, when I tried to save a page (this is still the single most common cause of crashes here at work), and just now I left my desk for a few minutes, and when I came back, SM was gone.  I had three tabs open, one to my gmail, one to My Yahoo, and one to educause.com (I think) - it was idle.

I am hoping to hear about the miracle of a fix RSN....  :-)

No answer required - I hope that this helps isolate the cause, though I don't think it will, so if it doesn't, just ignore it and press on.

Thanks.

Comment 8

[Wayne Mery (:wsmwk)]

mhr can you get a crash report id using current trunk build?
 http://support.mozilla.com/en-US/kb/Mozilla+Crash+Reporter

Comment 9

[Wayne Mery (:wsmwk)]

closing incomplete. please reopen with crash report id if you can reproduce using beta
 http://www.seamonkey-project.org/releases/2.0b1