This Seamonkey seems likely to crash when Chatzilla .9.7.7 is running

RESOLVED INCOMPLETE

Status

SeaMonkey
General
--
major
RESOLVED INCOMPLETE
12 years ago
10 years ago

People

(Reporter: John T, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061215 SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061215 SeaMonkey/1.5a

Several times in the past few days (twice today) I was browsing and using email OK, then started chatzilla v. .9.7.7 which ships with recent Seamonkeys, and twice without warning or messages, all Seamonkey windows closed. I am going to try browsing and email some more, but for now want to suggest that there may be a problem with chatzilla .9.7.7. This never happened while using .9.7.5.


Reproducible: Always

Steps to Reproduce:
1. Start Seamonkey either in browser and email windows
2. Browse, do email, observe satisfactory performance for perhaps hours.
3. Open Chatzilla window, log onto a chat network and chatroom (#seamonkey on moznet for example) and chat.

Actual Results:  
Seamonkey seems to crash with no warning shortly after opening chatzilla window and using it in a chatroom (channel). Talkback does not appear when this happens.

Expected Results:  
No instability should be introduced by opening chatzilla .9.7.7. Seamonkey should continue running as long as the user requests.

I used a build dated 11-26 or 11-25 satisfactorily, tried a 12-9 build, a 12-13 build. and this one, 12-15. These versions had crashing problems including the high likelihood of crashing while using the chatzilla included in the build.

Comment 1

12 years ago
you're probably seeing bug 363239
John, are you still seeing this in a recent trunk build (2.0a1pre) with the version of Chatzilla that ships with it (at the moment, 0.9.81)?

If you aren't, please resolve this bug WORKSFORME.
No reply to comment #2 in 3 weeks - resolving INCOMPLETE.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.