#715 closed defect (duplicate)

bug in glib event loop management

Reported by: Emanuele Giaquinta Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 3.0
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:


To reproduce:

  • create a jabber account and set as server ""
  • execute 'account x on' and 'account x off'

glib starts logging indefinitely

(process:PID): GLib-WARNING : poll(2) failed due to: Bad file descriptor.

The problem is possibly caused by the fact that

  • 'proxy_connect_none' creates an io watcher with 'b_input_add'
  • 'gaim_io_connected' is never called
  • 'account x off' triggers a 'closesocket' on the fd.

Since 'gaim_io_connected' is not called the io watcher is not removed and thus poll barfs, as the fd is invalid after 'closesocket'.

Attachments (0)

Change History (1)

comment:1 Changed at 2010-11-08T10:50:39Z by wilmer

Resolution: duplicate
Status: newclosed


Known issue. Will be fixed eventually, but really, libevent is preferred for larger-scale deployments where stability matters more.

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.