This problem has been driving me nuts for a while, so this morning I
removed /etc/X11, /usr/X11*, /Applications/Utilities/X11.app, and the
launchd entries, then downgraded to 2.2.3. Everything seems to be
working normally now.
Prior to that, I did also try the current beta for a week or so, but
that gave me the same results as 2.3.0.
I'll try newer versions at some point in the future, and report back
if the problem has gone.
Thanks, Gavin.
On 12 Aug 2008, at 17:06, Jeremy Huddleston wrote:
Is urxvt hanging on startup and consuming 100% cpu? If so, this is
probably because of a known kernel bug since 10.5.0.
If not, can you please take a sample (/A/U/Activity Monitor.app) of
the urxvt and X11 processes, so I can see where it's hanging.
On Aug 12, 2008, at 07:20, Gavin Panella wrote:
Hi,
For the last week or two - I can't remember exactly when, but it /
might/ coincide with the installation of Security Update 2008-005 -
urxvt consoles have been regularly hanging, sometimes after hours
of use, sometimes after a few seconds. Emacs also crashes, but less
frequently, and it just disappears; it doesn't hang. I hardly use
any other X applications so I haven't experienced other crashes.
I have installed urxvt from the rxvt-unicode package in MacPorts. I
have been the rxvt-unicode package for over a year and it has not
shown any instability before. Since the crashes began, I have
updated MacPorts (although I tend to keep reasonably current
anyway) and recompiled all dependencies (recursively) of rxvt-
unicode, including itself. The frequency of crashing hasn't
changed, and has become more frequent if anything. I have also
reinstalled X11 2.3.0 a couple of times.
Emacs runs on a Ubuntu guest running on VMWare, and is the standard
GTK-enabled Emacs for Ubuntu Hardy. I run it via `ssh -Y ...`.
When the urxvt processes hang, dtruss shows things happening when I
move the mouse over the window, but that's where my understanding
ends. The window contents are /not/ redrawn, and the mouse cursor
becomes completely invisible. The window can be moved and
minimized. However, to kill the process, neither SIGINT nor SIGQUIT
is enough; SIGABRT or SIGKILL are needed, or a restart of X. I have
a couple of SIGABRT crash logs and can forward one or both if they
could be useful, or I can generate more.
Is there anything else I can do to try and diagnose these hangs?
They seem to happen about 10-20 times per day at the moment, so I
should be able to get some useful information quite quickly. They
are seriously impeding my ability to work so I'm keen to figure
this out.
Thanks, Gavin.
_______________________________________________
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
