Opened 14 years ago

Closed 14 years ago

#105 closed Defect (Fixed)

Colloquy using up all CPU polling in select()

Reported by: anonymous Owned by: timothy
Component: Colloquy (Mac) Version: 2.0 (Mac)
Severity: Normal Keywords:
Cc:

Description

Recently (like today) Colloquy started spinning in select, using up all the CPU. ktrace shows:

25359 Colloquy CALL select(0x8,0xf00b0440,0xf00b04c0,0xf00b0540,0xf00b05c0)
25359 Colloquy RET select 0
25359 Colloquy CALL select(0x8,0xf00b0440,0xf00b04c0,0xf00b0540,0xf00b05c0)
25359 Colloquy RET select 0
25359 Colloquy CALL select(0x8,0xf00b0440,0xf00b04c0,0xf00b0540,0xf00b05c0)
25359 Colloquy RET select 0
25359 Colloquy CALL select(0x8,0xf00b0440,0xf00b04c0,0xf00b0540,0xf00b05c0)
25359 Colloquy RET select 0
25359 Colloquy CALL select(0x8,0xf00b0440,0xf00b04c0,0xf00b0540,0xf00b05c0)
25359 Colloquy RET select 0
25359 Colloquy CALL select(0x8,0xf00b0440,0xf00b04c0,0xf00b0540,0xf00b05c0)
25359 Colloquy RET select 0
25359 Colloquy CALL select(0x8,0xf00b0440,0xf00b04c0,0xf00b0540,0xf00b05c0)

It does not matter if I'm connected to a server or not. This starts at program startup.

2.0 (v2D9 3/20)

Change History (2)

comment:1 Changed 14 years ago by eridius

I asked for a sample. The ktrace is useless here since there's no way to tell where the select() is being called. Think you could provide?

comment:2 Changed 14 years ago by Rinoa

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in 2D16.

Note: See TracTickets for help on using tickets.