Re: 100% cpu usage on spawning xterm
Re: 100% cpu usage on spawning xterm
- Subject: Re: 100% cpu usage on spawning xterm
- From: Jeremy Huddleston <email@hidden>
- Date: Wed, 12 Dec 2007 10:40:18 -0800
No, it didn't. It's still there. It's not a problem with sshd or
xterm. I believe it's a problem with with ioctl spinning on a gettty
On Dec 12, 2007, at 10:21, Bill Janssen wrote:
By the way, I should note that installing 2.1.0.1 also fixed the sshd
problem for me.
Bill
Now, this is interesting... I noticed a timed out ssh connect to my
leopard box a few times and then noticed sshd consuming 100% as
well!
I'm fairly certain these events are related (as they both are most
certainly doing the same process to get a tty).
I've seen both these problems (the xterm and the sshd). I notice
that
if I kill the xterm, the csh I was running the xterm from continues
to
take 100%. Attaching to that and doing a sample (with Activity
Monitor) shows a sample like this:
Call graph:
881 Thread_2503
881 0x1cc2
881 0x4f5a
829 0x21dc
806 close$UNIX2003
806 close$UNIX2003
16 cerror
10 cerror
5 cthread_set_errno_self
5 cthread_set_errno_self
1 __error
1 __error
3 0x1591d
3 0x1591d
2 0x158f7
2 0x158f7
1 0x1591c
1 cerror
1 cerror
1 dyld_stub_close$UNIX2003
1 dyld_stub_close$UNIX2003
...
The other odd thing is that it always happens twice (either with the
xterm or the sshd); the third xterm or ssh always succeeds. Or any
succeeding one, as long as the first two are still around.
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden