Re: Performance slowdown when traversing UIElements under menu bar of Mail and some other apps
Re: Performance slowdown when traversing UIElements under menu bar of Mail and some other apps
- Subject: Re: Performance slowdown when traversing UIElements under menu bar of Mail and some other apps
- From: Bill Cheeseman <email@hidden>
- Date: Thu, 11 Nov 2010 12:00:04 -0500
On Nov 11, 2010, at 11:42 AM, Peter Lübke wrote:
> Ok, I didn't want to bother you with my calling code, but I mentioned:
> "In the calling method, I compare the returned object against the value I'm looking for and then release it by calling [value release]."
Yes, Christiaan pointed this out, too. I was skimming my email too fast and responded without focusing on the entire message. Sorry for any confusion.
> Besides from the important naming conventions discussion, let me repeat my key question:
> Why do some apps (Mail, Firefox) accumulate allocated memory in their own memory space when my app scans their AXUIElements? while other apps don't!
>
> Any clues?
I have made extensive use of the Accessibility API for several years. In my experience, developers of accessible applications (including Apple) sometimes make mistakes. It is possible that Mail and Firefox contain some accessibility-related bugs that show up as leaks when you access their internal support for the Accessibility API. Mail is full of custom UI elements, and custom UI elements require the application developer to provide custom code supporting accessibility. I don't use Firefox, but I did confirm as recently as last year that it did not support Accessibility at all at that time, although I understand that support was high on their to-do list and presumably has now been added. I assume Firefox has plenty of custom UI elements, too, and since their supporting code for Accessibility is new the chance of bugs is high.
My UI Browser utility will help you to explore the nature and extent of Accessibility API support in Mail, Firefox, and other target applications. However, UI Browser does not give you any help tracing memory management issues in target applications. Download a 30-day free trial version of UI Browser at <http://pfiddlesoft.com/uibrowser>. You can get similar but less extensive help from Apple's free UIElementInspector application (and see its sample code).
--
Bill Cheeseman - email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden