190899 - Chatzilla spins CPU on non-port specific IRC URL, after connecting to a non-default network port

Status: RESOLVED FIXED

(Other Applications Graveyard :: ChatZilla, defect)

Description

[Urban A. Haas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030127
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030127

I had automatic "Open at Startup" windows. I was connected to an IRC Server
irc.umn.edu:6669 and had channel URLs AIX channel on irc.umn.edu, which were
just context menu saved from a previous IRC session.

When reconnecting, Chatzilla connected to irc.umn.edu on port 6669. When trying
to open channel AIX (without being channel specific), Chatzilla spun the CPU at
100% and did nothing.

Reproducible: Always

Steps to Reproduce:
1. Define an IRS server with a non-standard port, such as irc.umn.edu:6669.
2. Have the network autostart
3. Have some channels with the port of 6669
4. Have others without a channel reference.

Actual Results:  
Spun CPU at 100%

Expected Results:  
Should have used the existing port 6669, since the network was connected. I
would say, if the port is missing from a channel, then the port the network
connection was opened on should be used. I'm betting since it wasn't explicitly
mentioned, it assumed 6667.

Comment 1

[Urban A. Haas]

Similiar to bug 156928, but this is attempting to use the same port, not have
multiple ports opened.

Comment 2

[James Ross]

Could the reporter please try out a version of Chatzilla from
http://www.hacksrus.com/~ginda/chatzilla/ of at least version 0.9.29 (preferably
try the latest version, 0.9.35). These versions have the patch for bug 156928 in
them, and it may have fixed this problem too.

Comment 3

[Robert Ginda]

*** Bug 217962 has been marked as a duplicate of this bug. ***

Comment 4

[Carl Brewer]

I downloaded 0.9.35 and the bug is gone.  Thankyou

Comment 5

[James Ross]

Marking FIXED as per comments. If this is not true, please reopen.