Ticket #1116 (new defect)

Opened 1 year ago

Last modified 2 weeks ago

Colloquy eats 95%+ of CPU

Reported by: Sparks Assigned to: timothy
Priority: highest Component: Chat Core (IRC)
Version: Latest 2.1 Severity: critical
Keywords: Cc: beej, danchr, xenon, grahamperrin

Description

A bit of testing shows that this happens on Tiger with the Safari 3 WebKit? installed, but a (very) cursory check does not seem to have this happen on Leopard.

Periodically (often right after startup, but sometimes after hours running) Colloquy will begin to eat 95% or more of the CPU. Colloquy itself does not become in any way unresponsive or beachball, but the CPU of the machine is driven to the point that the fans kick in, and top or any other form of process monitor shows Colloquy pegging the CPU. Needless to say, this makes other software turn sluggish!

Disconnecting from everything, closing all windows, and basically making Colloquy stop doing everything does NOT correct this; only an entire quit and restart will solve the problem, and even then a restart seems likely to immediately peg again.

Attachments

colloquy_sample.txt (93.4 kB) - added by beej on 10/24/07 10:35:57.
output of "sample Colloq 5 20 -file colloquy_sample.txt"
colloquy_spin_control.txt (232.4 kB) - added by w0mbat on 12/06/07 17:57:35.
478s spin control report. indentation removed due to file size limitation

Change History

10/10/07 17:46:58 changed by beej

cc me

10/15/07 01:21:51 changed by timothy

  • cc set to beej.

10/24/07 10:35:57 changed by beej

  • attachment colloquy_sample.txt added.

output of "sample Colloq 5 20 -file colloquy_sample.txt"

10/24/07 10:39:48 changed by beej

the colloquy_sample.txt that i just attached is from Colloquy 2.1 going into this all too familiar tailspin. this time it happened as my C2D blackbook came out of sleep in closed lid mode. Colloquy itself was "Not Responding" according to OS 10.4.10 and had to be force quit.

12/06/07 17:52:10 changed by w0mbat

I'm having the same problem, except that Colloquy does become unresponsive. The app will spin for at least 5 minutes. Compiled from revision 3769.

MacBook? Pro, OS X 10.4.10, Safari 2

12/06/07 17:57:35 changed by w0mbat

  • attachment colloquy_spin_control.txt added.

478s spin control report. indentation removed due to file size limitation

01/07/08 16:55:38 changed by danchr

  • cc changed from beej to beej, danchr.
  • component changed from Colloquy (GUI) to Chat Core (IRC).

I experienced this very thing earlier today; Colloquy remained responsive and hogged every single CPU cycle it could get. I made a sample using Instruments.app, attached below. I was talking to akempgen whom I suspect is a Colloquy developer, and he said I “…really needed to talk to xenon about stuff like that.” AFAICT this bug is subscribed to him, all the more reason to think this is the same issue.

As far as I can tell, the culprit is [MVIRCChatConnection(MVIRCChatConnectionPrivate) _ircRunloop] from ChatCore. Judging from the source code for it, I suspect the issue may be an “opposite deadlock” so to speak; that for some reason, those locks and runloops do not suspend execution.

Environment:

  • Colloquy v2.1 (3761)
  • Mac OS X 10.5.1
  • 768MB RAM
  • 1.25GHz eMac G4

Input Managers:

  • SIMBL
  • SafariBlock

SIMBL plugins:

  • GrowlSafari
  • Keywurl
  • Twicetab

01/07/08 17:01:18 changed by danchr

Instruments.app sample, too large to upload.

01/10/08 10:04:14 changed by beej

  • cc changed from beej, danchr to beej, danchr, xenon.

01/10/08 10:04:57 changed by beej

xenon: was akempgen right about you being the person to talk to about this issue? it's very annoying :(

02/07/08 17:14:32 changed by beej

there is some evidence that the beachballing i'm seeing has to do with transcript indexing. i was set to "One File Per Session Day" logging, which is apparently broken (#1010, #1115). at the suggestion of bogo_lode from #colloquy, i changed that to "One File Per Session" and moved the old logs out of the way.

/me crosses fingers

11/15/08 07:00:25 changed by grahamperrin

  • cc changed from beej, danchr, xenon to beej, danchr, xenon, grahamperrin.

@ beej:

Are your fingers still crossed or has the workaround been successful for you?

11/15/08 07:20:45 changed by grahamperrin

http://www.diigo.com/annotated/fe243d2973638121dbe1018717f37608 highlights my own beach ball in ticket:1210.