ChatZilla crashes the browser

RESOLVED WORKSFORME

Status

Other Applications
ChatZilla
--
critical
RESOLVED WORKSFORME
16 years ago
14 years ago

People

(Reporter: Nino, Assigned: Robert Ginda)

Tracking

({crash})

Trunk
x86
Windows 2000
crash

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
Opened: Mozilla 0.9.8 browser (no web page accessed yet)
        Chat Zilla

Problem: while listing the channels on Dalnet network ChatZilla got frozen
causing the closure of the browser window, too.
(I have taken a screenshot, could email it to the developer)

Comment 1

16 years ago
Reporter:

1. Please set severity level to "critical", and add the keyword "crash".
2. Which IRC server did you attempt to connect to?
3. If you believe the screenshot useful, please attach it to this bug report
   by clicking the link "Create a New Attachment" above.

Thank you for using Bugzilla!

Updated

16 years ago
Severity: major → critical
Keywords: crash
(Reporter)

Comment 2

16 years ago
Created attachment 68544 [details]
Screenshot!

I have just repeated the procedure and the same thing happened:

After opening the browser, I started Chatzilla and then typed the following:
/attach dalnet
/list
..................... Craaassssshhh!!!

I therefore don't know which server did I connect to, but it must be the one
already set as defualt (perhaps you would know).

Worth to be mentioned, (while the channels were being listed in the main
chatzilla screen (shortly before crashing), I couldn't do anything with the
browser - it appeared to be already frozen.

Comment 3

16 years ago
It didn't actually crash, it just used up so much CPU time that the other parts
of the browser and the UI don't get a chance to respond.  (And it doesn't
respond to Windows, which is why you got that message.)

Comment 4

16 years ago
wfm 20020302
please try a newer build...
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
Product: Core → Other Applications
You need to log in before you can comment on or make changes to this bug.