On Sun, 30 Apr 2023 at 01:10, James Addison <j...@jp-hosting.net> wrote: > > I don't have much to (bug)report here yet, but have begun using > espeakup as a screen reader via Orca in GNOME. CPU usage on the > machine seemed relatively high, and at times text input became > unresponsive (both in-browser, where both window scrolling and > input-field text entry became unreliable). The espeakup process also > segfaulted once (this was over approximately 8 hours or so of > continuous usage).
A missing ingredient from that soup of words: "(both in-browser, where both window scrolling and input-field text entry became unreliable, _and also within a gnome-terminal session_)." (I think it's important to include that detail, because it suggests to me that the cause of the high-resource-usage and/or input interaction problems is not specific to one desktop application, and could be an issue with Debian's espeakup/espeak-ng, and/or and their interaction with the GNOME desktop. CPU usage decreases to normal levels and expected input behaviour is restored after screenreading is turned off)
