Closed
Bug 325190
Opened 19 years ago
Closed 18 years ago
Chatzilla crashes on opening if you have too many windows/tabs open in Firefox.
Categories
(Other Applications :: ChatZilla, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: supah_glu, Assigned: rginda)
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 When I try to open chatzilla with more than 10 tabs in firefox open it crashes. I have two channels on one server set to open at when chatzilla starts but it doesn't even get that far, the *client* tab opens as a grey blank space and the cpu usage goes to 100% and stays there. Then the "send error report" window comes up and firefox crashes. The problem might be that I have only 512MB ram, when I closed all the tabs but this one it stopped crashing. This is more of a problem with firefox being a general memory hog than chatzilla screwing up but if you can convince someone that firefox should use less memory that'd be great. Reproducible: Always Steps to Reproduce: 1.Open many tabs/windows 2.Try to open chatzilla 3.Wait a while open more tabs and repeat. Actual Results: Chatzilla freezes up and Firefox crashes. Expected Results: Opened the server and then the two channel tabs. I have 5 scripts (chattytunes, geoip, gspel, 8ball and dice) and am using a custom motif and the two channels in the one server opening when chatzilla starts.
Comment 1•19 years ago
|
||
Hate to tell you, but this really can't be anything to do with us. Until we can blame someone properly, please put Talkback IDs in here, too - a crash is useless without a TB ID.
Comment 2•19 years ago
|
||
Reporter, please supply more information. This bug is useless as-is. I will resolve it as INVALID in a week's time if there has been no progress.
Comment 3•18 years ago
|
||
Resolving per comment #2
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•