Ticket #976 (new defect)

Opened 2 years ago

Last modified 2 years ago

Cycling a channel doesn't work and can cause CPU spikes in some circumstances

Reported by: Scaredy Assigned to: timothy
Priority: normal Component: Colloquy (GUI)
Version: Latest 2.1 Severity: normal
Keywords: Cc:

Description

The circumstances I was able to make this occur:

  • Have Colloquy setup to auto-join a single channel and do not join any others
  • Start Colloquy fresh
  • Use /cycle #channel (Using /cycle without parameters or /hop don't cause it)
  • Colloquy will rejoin channel, then part it again, which is not the expected behaviour
  • Upon rejoining the channel manually, the CPU may spike. This part doesn't happen 100% of the time.

I'm attaching a sample in case it may aid in troubleshooting.

Attachments

Sample of Colloquy.txt (20.1 kB) - added by Scaredy on 01/24/07 18:13:26.

Change History

01/24/07 18:13:26 changed by Scaredy

  • attachment Sample of Colloquy.txt added.

03/28/07 13:29:16 changed by Rinoa

  • priority changed from low to normal.
  • severity changed from minor to normal.

Related to #728.