The Mozilla SeaMonkey browser used to hang regularly with a futex_wait_queue_me status in the System Monitor, but since about release 2.5 a few months ago the problem has become rare to non-existent. The coders must have found the problem and fixed it, although they never give details of what they did, cloaking it under the general term of "stability fixes". It was probably some stupid minor coding oversight or omission that they're too embarrassed to fess up to. My suspicion is that it was a mis-handling of time data, because the problem was most severe from about 10 a.m. to midnight daily and would get worse toward the end of the month. The futex_wait_queue_me hangs might have timed out in 18-24 hours, allowing SeaMonkey to continue on its own, but who wants to wait that long? I used System Monitor to kill SeaMonkey dozens, nay, hundreds of times. It was sickening.
The thing to do with open source software is to complain loudly and frequently and file bug reports until someone notices and tackles the problem.
Last edited by Andrew4096; 01-19-2012 at 03:48 PM.