To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=55003
                  Issue #:|55003
                  Summary:|Memory leaks in Accessibility API
                Component:|api
                  Version:|OOO 2.0 Beta2
                 Platform:|PC
                      URL:|
               OS/Version:|Windows XP
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|code
              Assigned to:|sw
              Reported by:|ombak





------- Additional comments from [EMAIL PROTECTED] Fri Sep 23 08:20:40 -0700 
2005 -------
I'm currently developping a Java software which is going to use the OpenOffice 
Accessibility API to get informed of any changes occuring in the current 
OpenCalc document.
The Accessibility part of my code is inspired by your SSR(Simple Screen Reader) 
sample.
Memory leaks issues I've been facing are also present in the SSR project. It 
seems that it is linked to the use of Accessibility API.
You can see that when you launch the SSR, memory usage of soffice.bin is 
increasing of around 1MB by second, but if you change the current sheet, then 
the memory taken by the process will come down to around 40 to 50 megs.

Should you require further details, please feel free to contact me.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to