https://bugs.documentfoundation.org/show_bug.cgi?id=153131
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|[email protected] |[email protected] |desktop.org | Status|NEW |ASSIGNED --- Comment #74 from Michael Weghorn <[email protected]> --- (In reply to Michael Weghorn from comment #58) > I can reproduce on Windows 10 (Version 22H2 (OS Build 19045.3448)) as well. > > At first glance, it looks like Windows Speech Recognition tries to iterate > over all of the cells of the table (or maybe "just" over the first > 2147483648 ones, since that's the max amount that the 32-bit API allows to > return in `CMAccessible::get_accChildCount`, or whatever other limit Windows > Speech Recognition or some library underneath have). > > With a breakpoint in `CMAccessible::get_accChild` [1], I see this getting > called e.g. with `varChild.lVal = 1141`, then `varChild.lVal = 1142`, etc. > And after letting it run for a while with `varChild.lVal = 3694`, then > `varChild.lVal = 3695`,... Backtrace below. > > I can't see anything obviously wrong on LO side here, it seems to be getting > requests via the accessibility API that it is handling correctly. > > Without knowing any further details on what Windows Speech Recognition is > doing here, it's hard to further analyze this and I tend to think that > Windows Speech Recognition shouldn't be requesting all of the cells > (accessible children of the table). >From what I can see, https://gerrit.libreoffice.org/c/core/+/181370 seems like a good enough solution/workaround for now. At least it fixes the crash with Windows Speech Recognition on Windows 10 that I can reproduce and it doesn't seem to be causing any issues with the NVDA screen reader in my tests either. I cannot reproduce any freeze on Windows 11 (not even with "Voice access" enabled in the Windows accessibility settings) so can't test myself whether it helps for the cases of tdf#165131, tdf#165137, tdf#165155 (where it's still unclear what is triggering the issue). The "Offer suggested actions" (tdf#158691) feature for Windows 11 is currently only available in North America according to [1], so I can't test that one either. [1] https://support.microsoft.com/en-us/windows/use-suggested-actions-on-your-pc-486c0527-3395-4b40-b304-f1e3cbe2f404 -- You are receiving this mail because: You are the assignee for the bug.
