810940 - Crash (no crash report generated)

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[John T]

User Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120909 Firefox/15.0.1 SeaMonkey/2.12.1
Build ID: 20120909051705

Steps to reproduce:

With recent versions of Seamonkey (2.12.x?. 2.13 and 2.14), I've been having crashes that don't invoke the crash report generation code. I think it happens when I have more than one window open, but it doesn't happen as a result of any actions I can identify. I might be trying to switch from one browser window to another, load another web page, etc. The only thing I can say with confidence is that the problem doesn't seem to be related to email. I've gone back to 2.12.1 because it seemed just too common with 2.14.


Actual results:

The browser becomes quite unresponsive, slow to display typed text, switch windows by clicking, and seeming to be waiting for a slow network event. I had quite a few crashes two days ago with extra-slow networking.

Is there any way to set the browser to report bad packets to the user? The day was windy and it's conceivable that my dsl connection had a line problem resulting perhaps in frequent requests to resend packets.


Expected results:

I would expect the browser to respond quickly to mouse clicks and keyboard text entry, and not wait interminably for a response from the network. Does network stuff run in the same thread as keyboard/mouse/desktop user activity?

Comment 1

[John T]

I ran a memory-testing program yesterday to see if there was any detectable bad memory, and got zero errors. The crashes are probably not due to a hardware problem.

Comment 2

[Phoenix]

Anything in about:crashes? If yes, provide links to crash reports please

Comment 3

[Matthias Versen [:Matti]]

Getting slower and slower followed by a crash sounds like you have a memory leak.
Do you see a high used memory count in about:memory ?

Comment 4

[Tony Mechelynck [:tonymec]]

John: Is it a crash or a hang? The difference is that with a crash, the program is killed, while with a hang, it still occupies memory with either low CPU (waiting on something which never happens) or high CPU (running in circles chasing its own tail, so to speak, but doing nothing useful).

Try

   ps -lC seamonkey

at a shell prompt. If it's a crash, you'll see only column headers. If it's a hang, you'll also get a line about a "seamonkey" process which has a certain PID, a certain PPID, etcetera.

Comment 5

[Tony Mechelynck [:tonymec]]

P.S. If your whole X11 display gets blocked, you may perhaps still get a shell prompt by hitting Ctrl+Alt+F2 and (if necessary) logging in. It's text-only but it's enough to run ps.

Comment 6

[Wayne Mery (:wsmwk)]

reporter doesn't reply