[xmonad] Issue 197 in xmonad: Blocking on nextEvent stops other threads from running

codesite-noreply at google.com codesite-noreply at google.com
Sat Jun 28 04:24:11 EDT 2008

Issue 197: Blocking on nextEvent stops other threads from running

New issue report by asampson:
What steps will reproduce the problem?

>From main, start another lightweight thread with forkIO that does something
periodically (e.g. forever (putStrLn "hello, world" >> threadDelay 500000)).

What is the expected output? What do you see instead?

The new thread only gets a chance to run when xmonad receives an event,
since xmonad spends most of its time blocked inside the Xlib bindings.

What version of the product are you using? On what operating system?

Darcs xmonad as of 2008-06-28, on Linux, with GHC 6.8.2.

I've attached a patch that makes xmonad wait on the X file descriptor when
there aren't any events waiting to be processed.

	do-not-block-2.patch  4.0 KB

Issue attributes:
	Status: New
	Owner: ----
	Labels: Type-Defect Priority-Medium

You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:

More information about the xmonad mailing list