This behaviour of opening too many files happens on other occasions too, not
just with mail notification. For instance, I have just clicked on the help
button of a configuration dialog and bonobo-activation-server is on an
infinite loop exactly as described above. This is an excerpt of an strace of
the process:
accept(32, 0xbffaa2a0, [110]) = -1 EMFILE (Too many open files)
poll([{fd=21, events=POLLIN}, {fd=30, events=POLLIN|POLLPRI}, {fd=32,
events=POLLIN|POLLPRI, revents=POLLIN}, {fd=3, events=POLLIN|POLLPRI},
{fd=27, events=POLLIN|POLLPRI}, {fd=35, events=POLLIN|POLLPRI}, {fd=36,
events=POLLIN|POLLPRI}, {fd=34, events=POLLIN|POLLPRI}, {fd=37,
events=POLLIN|POLLPRI}, {fd=39, events=POLLIN|POLLPRI}, {fd=40,
events=POLLIN|POLLPRI}, {fd=38, events=POLLIN|POLLPRI}, {fd=41,
events=POLLIN|POLLPRI}, {fd=43, events=POLLIN|POLLPRI}, {fd=44,
events=POLLIN|POLLPRI}, {fd=42, events=POLLIN|POLLPRI}, {fd=45,
events=POLLIN|POLLPRI}, {fd=46, events=POLLIN|POLLPRI}, {fd=47,
events=POLLIN|POLLPRI}, {fd=51, events=POLLIN|POLLPRI}, {fd=60,
events=POLLIN|POLLPRI}, {fd=61, events=POLLIN|POLLPRI}, {fd=122,
events=POLLIN|POLLPRI}, {fd=123, events=POLLIN|POLLPRI}, {fd=124,
events=POLLIN|POLLPRI}, {fd=125, events=POLLIN|POLLPRI}, {fd=179,
events=POLLIN|POLLPRI}, {fd=181, events=POLLIN|POLLPRI}, {fd=183,
events=POLLIN|POLLPRI}, {fd=186, events=POLLIN|POLLPRI}, {fd=189,
events=POLLIN|POLLPRI}, {fd=190, events=POLLIN|POLLPRI}, ...], 39, -1) = 1
accept(32, 0xbffaa2a0, [110]) = -1 EMFILE (Too many open files)
poll([{fd=21, events=POLLIN}, {fd=30, events=POLLIN|POLLPRI}, {fd=32,
events=POLLIN|POLLPRI, revents=POLLIN}, {fd=3, events=POLLIN|POLLPRI},
{fd=27, events=POLLIN|POLLPRI}, {fd=35, events=POLLIN|POLLPRI}, {fd=36,
events=POLLIN|POLLPRI}, {fd=34, events=POLLIN|POLLPRI}, {fd=37,
events=POLLIN|POLLPRI}, {fd=39, events=POLLIN|POLLPRI}, {fd=40,
events=POLLIN|POLLPRI}, {fd=38, events=POLLIN|POLLPRI}, {fd=41,
events=POLLIN|POLLPRI}, {fd=43, events=POLLIN|POLLPRI}, {fd=44,
events=POLLIN|POLLPRI}, {fd=42, events=POLLIN|POLLPRI}, {fd=45,
events=POLLIN|POLLPRI}, {fd=46, events=POLLIN|POLLPRI}, {fd=47, IN|POLLPRI},
{fd=27, events=POLLIN|POLLPRI}, {fd=35, events=POLLIN|POLLPRI}, {fd=36,
events=POLLIN|POLLPRI}, {fd=34, events=POLLIN|POLLPRI}, {fd=37,
events=POLLIN|POLLPRI}, {fd=39, events=POLLIN|POLLPRI}, {fd=40,
events=POLLIN|POLLPRI}, {fd=38, events=POLLIN|POLLPRI}, {fd=41,
events=POLLIN|POLLPRI}, {fd=43, events=POLLIN|POLLPRI}, {fd=44,
events=POLLIN|POLLPRI}, {fd=42, events=POLLIN|POLLPRI}, {fd=45,
events=POLLIN|POLLPRI}, {fd=46, events=POLLIN|POLLPRI}, {fd=47,
events=POLLIN|POLLPRI}, {fd=51, events=POLLIN|POLLPRI}, {fd=60,
events=POLLIN|POLLPRI}, {fd=61, events=POLLIN|POLLPRI}, {fd=122,
events=POLLIN|POLLPRI}, {fd=123, events=POLLIN|POLLPRI}, {fd=124,
events=POLLIN|POLLPRI}, {fd=125, events=POLLIN|POLLPRI}, {fd=179,
events=POLLIN|POLLPRI}, {fd=181, events=POLLIN|POLLPRI}, {fd=183,
events=POLLIN|POLLPRI}, {fd=186, events=POLLIN|POLLPRI}, {fd=189,
events=POLLIN|POLLPRI}, {fd=190, events=POLLIN|POLLPRI}, ...], 39, -1) = 1
There are other actions which will trigger this behaviour too, and I run
into this every few days. So I think this bug should be reassigned to
libbonobo2-common. I have version 2.14.0-4 of the libbonobo2-common package.
--
[]'s
Thiago Jung Bauermann