Closed Bug 520110 Opened 15 years ago Closed 15 years ago

Chatzilla should report netsplits differently, it stalls firefox and chatzilla until the split is over

Categories

(Other Applications :: ChatZilla, defect)

1.9.1 Branch
x86
Windows Vista
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 461404

People

(Reporter: charitwo, Assigned: rginda)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 4.0.20506)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 4.0.20506)

This is very frustrating, irssi uses a magical two lines. One for the splits, and another for the joins, and gives you the option to show more if you really are curious. Chatzilla should function no differently and should not stall during these occurrences. This becomes more prevalent on larger networks in which the user occupies multiple channels. Anywhere from 10 users to 1500, and the users that split from either of those ranges makes browsing completely impossible.

Reproducible: Always

Steps to Reproduce:
1.Launch Firefox
2.Launch ChatZilla
3.Be using Chatzilla during a netsplit, the stall is longer and more annoying when occupying multiple, LARGE channels.
Actual Results:  
Firefox stalled.

Expected Results:  
Reported it in as few lines as possible and allowed the end user to browse normally regardless of the splits that were happening.
OK, so how is this our fault? Please talk to chatzilla.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
CZ is a Mozilla.org addon, it comes with SM as default
Assignee: nobody → rginda
Status: RESOLVED → UNCONFIRMED
Component: General → ChatZilla
Product: Firefox → Other Applications
QA Contact: general → chatzilla
Resolution: INVALID → ---
Version: unspecified → 1.9.1 Branch
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.