https://bugs.documentfoundation.org/show_bug.cgi?id=153131
--- Comment #72 from Michael Weghorn <[email protected]> --- (In reply to Stéphane Guillou (stragu) from comment #71) > Settings to "high - major" as it's a freeze from a common operation. > > Michael, Mike: do you think this is the same source cause as a memory > increase when "offer suggested actions" is on? See bug 158691 and ady's > comment 67. See comment 58, comment 60 and comment 61 for a first analysis and the potential cause of the freeze. (Speech recognition querying an insane amount of children/cells.) (In reply to ady from comment #69) > Regarding my "not-our-bug" comment, it is just a possibility, that some > would suggest such status (considering that it is not set to new, and I > still don't know why). Since the report was/is not set to new, maybe someone > would think that all these symptoms should rather be solved by MS. Maybe the > problem is really not at all a bug in LO, but IMHO it would be better to try > to find some way to make it work anyway, for the reasons I mentioned before > in my prior comment. As mentioned in comment 61, I still think it would be worth trying to report to Microsoft at least, and see whether they can/will do anything about it. [My hope was that somebody with particular interest in this bug would go ahead and do this, but if nobody else is interested in doing that, I can add that to my list of things to do at some point next year.] It may be they don't. And I don't say that the LO side shouldn't change, but as described in more detail in the above-mentioned comments, I currently don't see a straightforward way to avoid the problem without the risk of breaking other use cases. Of course, if anybody has any great idea, please don't hesitate to implement that (or at least mention it here), but at least my main focus so far was on more actionable things, while this one here was mostly one of the "wait for further input and potentially revisit later" kind. The discussion in https://gitlab.gnome.org/GNOME/gtk/-/issues/6204 might provide some helpful input (see in particular the comments from the Orca maintainer, Joanmarie Diggs), but that's also still ongoing. -- You are receiving this mail because: You are the assignee for the bug.
