Re: [Solved] -validateMenuItem: like crazy, hogs CPU for 1st minute

2010-03-19 Thread Jerry Krinock
On 2010 Mar 19, at 12:28, Eric Schlegel wrote: > It looks to me that some other process on your system is using the > Accessibility API to inspect your menu structure. That's the > "_XCopyAttributeValue" and subsequent callstack in your first sampler output. > > Do you have Accessibility enabl

Re: -validateMenuItem: like crazy, hogs CPU for 1st minute

2010-03-19 Thread Eric Schlegel
It looks to me that some other process on your system is using the Accessibility API to inspect your menu structure. That's the "_XCopyAttributeValue" and subsequent callstack in your first sampler output. Do you have Accessibility enabled? What happens if you disable it? -eric On Mar 19, 2010

Re: -validateMenuItem: like crazy, hogs CPU for 1st minute

2010-03-19 Thread Jerry Krinock
I just realized I should have included the Sampler output. Here it is. You see after the 1643 samples of MenuData::GetNamedAccessibleAttributeSelf, it breaks into two branches, both of which end up in -validateMenuItem: Analysis of sampling pid 25997 every 1 millisecond 1691 Thread_798599 Di

-validateMenuItem: like crazy, hogs CPU for 1st minute

2010-03-19 Thread Jerry Krinock
This morning I was noticing that text fields could not keep up with my typing into them. But this only occurs during the first minute or so after my app is launched, and sampling shows that the main thread is spending most of its time in my app delegate's -validateMenuItem:. I do have a couple