Hi,
First, I don't know anything about the actual
makeup of all the voice over processes. That
said, here's what not responding means in the
context of Activity Monitor.
For the screenreader process, it is actually
asleep. YOu can use the ps terminal command to
confirm this. It's not all that uncommon to see
this in compression utilties or QuickTime codecs.
The real problem is Activity Monitor trying to
make the data presentable to the majority of
users. It makes some assumptions about the state
of the process from several data points and
translates that to what you see in Activity
Monitor. So, there's no real call for "not
responding" in the interface. Alas, ignore the
not responding status unless it really is an
application process or you see other symptoms.
Best,
Scott
At 1:04 PM -0500 3/7/08, David Poehlman wrote:
ester, you are right, the max update is 5 sec.
----- Original Message -----
From: "Esther" <[EMAIL PROTECTED]>
To: "General discussions on all topics relating to the use of Mac OS X by
theblind" <[email protected]>
Sent: Friday, March 07, 2008 12:11 PM
Subject: Re: Strange Quandary
Hi Cara,
I'm guessing that the Activity Monitor program didn't get a response
on status within the update time because of VoiceOver i/o. It's like
when you use the "Start speaking" from the Services Menu on a
long piece of selected text. You're not going to get any other
status information until your machine finishes "speaking its piece".
There's some feature like "Update Frequency" that you can set under
the View menu and maybe with larger intervals between report
updates you're more likely to get the status report from screenreaderd?
Just guessing here.
Cheers,
Esther
On Mar 07, 2008, at 06:51AM, Cara Quinn wrote:
Just for the heck of it, I ran activity monitor after reading the
notes about it and found that the screenreaderd process reports as
being hung or not responding. What does this mean? I'm obviously
using VO as we speak, so it sure doesn't seem hung to me! lol!
I'm assuming this is some other aspect of it, but shouldn't it show
as responding instead of not?
Thanks for your feedback.
Have an awesome one!
Smiles,
Cara :)
--
--Scott
