Issue 125355 - Checking for too many Accessible children in parallel seems to bring the accessibility api in a dead lock
Summary: Checking for too many Accessible children in parallel seems to bring the acce...
Status: UNCONFIRMED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 4.1.0
Hardware: PC Windows 7
: P3 Normal
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on: 125392
Blocks:
  Show dependency tree
 
Reported: 2014-08-05 11:43 UTC by Jens Bornschein
Modified: 2014-08-08 13:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.0
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Jens Bornschein 2014-08-05 11:43:06 UTC
When I'm checking all accessible child elements (XAccessible) of an XAccessibleContext (var c = haystack.getAccessibleChild(i);) via the cli api from C# the api seems to fall into some kind of dead lock. The OpenOffice process stops and doesn't response for any user interaction. When I abort my requesting application OpenOffice runs normally from this point.

I'm checking every available XShape on an XDrawPage for its XAccessible counterpart in parallel, starting the search from the base XAccessible which I have received from the XDrawPagesObservers Model ComponentWindow. Testing all elements serial will take too much time. The time until it hangs on isn't every time the same. I don't found any rule when it starts hanging.

In my testes I have a draw doc width circa 30 objects, building (incl. bézier curves for text) nearly 100 objects in the navigation tree.
Comment 1 Jens Bornschein 2014-08-08 13:36:21 UTC
the issue 125392 seems to be the reason