On 2/11/07 10:48 AM, "Ben Byer" <email@hidden> wrote:
> I've had a couple of reports of this -- sometimes it causes X11 to
> start chewing up 100% of the CPU time, sometimes it seems to just
> hang. Sometimes it works, too! Really!
>
> Feel free to file a bug report. I'm looking into it, but can't say
> what's causing it -- maybe some sort of race condition?
Excellent, so it's not just me.
It certainly seems like a race condition of sorts. Also, at times, X11 will
start with a display of :1 .
I must admit that I never looked at CPU usage.
> This message is harmless -- it's just xterm informing you that the
> reason it died was that you killed the X server.
I realise this (old X hat), but it's happening occasionally at an odd place
in the cycle which makes me think race condition too:
1) Start Terminal.app, do work
2) Need an xterm, start xterm
3) X11.app starts
4) xterm execution hangs.
5) Kill X11.app, new X11.app spawns
6) xterm complains about server shutdown instead of spawning
Basically, at step 6, xterm will most of the time spawn in the new server.
If I had more time to dive in and try to find the problem, I would, but I'm
more in a position of just trying to give you as much information as
possible. This is my work laptop, and I have more pressing things to do,
like write technical documents... :/ (I'd much rather be diagnosing this
problem, believe me!)
Mike.
--
Mike Beattie <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden
This email sent to email@hidden
