Re: ion-statusd eating up 100% cpu
Tuomo Valkonen <[email protected]>
| Newsgroups | gmane.comp.window-managers.ion.general |
|---|---|
| Message-ID | <[email protected]> |
On 2008-06-23, Christian Glindkamp <[email protected]> wrote: > Exactly this seems to have happened now. Wouldn't it be possible, at > least as a workaround, to call select with a timeout or did I missed > something (I don't know the ion code base, I just skimmed through some > of the related code sections)? A fixed timeout as such does not properly remove the race condition, as it may take some time to reach that time, unless it's so short as to cause a busyloop. In principle, one could however do entirely without the timer signal, by adjusting the select timeouts suitably. But that's another change that's perhaps a bit too big for Ion3, and for Ion3+, instead of more work on libmainloop, I'd rather see a patch to use libevent. Also, there are other signals for which the race condition remains (it is there even now). pselect() is the correct solution. -- Tuomo