Re: [wmii] wmii-3.1 bug: libixp overload

From: Suraj N. Kurapati <>
Date: Tue, 19 Sep 2006 03:07:21 -0700

Hash: SHA1

Mauricio Fernandez wrote:
> On Tue, Sep 19, 2006 at 02:10:14AM -0700, Suraj N. Kurapati wrote:
>> Anselm R. Garbe wrote:
>>> On Tue, Sep 19, 2006 at 01:45:37AM -0700, Suraj N. Kurapati wrote:
>>>> In wmii-3.1, it is possible to overload libixp with lots of 9P
>>>> traffic, maintained _continuously_ for about a minute, such that it
>>>> freezes.
>>> Please check if tuning maxfiles in your Unix environment will
>>> increase this boundary (maybe the amount of fd's is exceeded).
>> By file descriptors, do you mean the number of sockets trying to
>> connect with libixp?
>> If so, I think the problem is the amount and rate of traffic, rather
>> than the number of sockets requesting connections. The reason is: I
>> can also reproduce the bug by pumping lots of traffic through a
>> single socket (one ruby-ixp connection).
> FWIW, I managed to freeze wmiiwm a few times when I modified ruby-wmii to use
> Ruby-IXP 0.1.

Same here.

> wmiiwm got hanged in ixp_send_message, since the write(2) syscall blocked.
> That was with wmii-3.1 + Ruby-IXP 0.1. I'll try to reproduce it with
> Ruby-IXP 1.0.2 and a more recent wmii.

By the way, Ruby-IXP 1.0.2 has its own problems (deadlock). The
latest in SVN (> r50) has been fixed accordingly, so use that
instead. Otherwise, you might be fighting with two bugs.
Version: GnuPG v1.4.2.2 (GNU/Linux)

Received on Tue Sep 19 2006 - 12:07:32 UTC

This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 16:14:09 UTC