Re: [orca-list] Orca Hangs When Trying to Read Large Text File in Pluma

[Joanmarie Diggs <jdiggs igalia com>]

Unfortunately, we need to pay attention to text insertion events and 
caret moved events because normally they are not bogus and often should 
be presented to you. So we cannot stop listening for them.

When bogus (or otherwise completely useless) events do come in, the best 
Orca can do is immediately discard them as bogus rather than doing extra 
work to process them.

Once the app itself becomes not responsive to AT-SPI2 (the 
dead-accessible problem), Orca cannot magically make that app become 
responsive.

If Gtk stops flooding Orca with these events, then Orca won't have to 
discard them and maybe the app will remain responsive to AT-SPI2. So 
hopefully Hypra (or someone else) can fix this in Gtk.

--joanie

On 3/14/20 13:56, Arkadiusz Kozioł wrote:
> So you can't do anything with this at-spi2 events?
>
> W dniu 14.03.2020 o 18:35, Joanmarie Diggs pisze:
> > Not 100% sure. Gtk (I assume) is being super spammy, not just with 
> > text-insertion events (1 event for every 8192 characters inserted), 
> > but also with caret-moved events because Gtk (I assume) is emitting a 
> > caret-moved event after each insertion.
> >
> > But it looks like it might be an AT-SPI2 one as well. Because at some 
> > point in the flood, we go from getting valid events to getting events 
> > from "dead" accessibles. For instance:
> >
> > 13:20:39.753794 - EVENT MANAGER: object:text-changed:insert for [DEAD] 
> > in [DEAD] (10764288, 8192, 
> > 8wekyb3d8bbwe/AppCS/Assets/ModularMusic/Classic_00/music_Neutral_01_LOOP_E.wma: 
> > OK
> >
> > 13:20:39.753950 - EVENT MANAGER: object:text-caret-moved for [DEAD] in 
> > [DEAD] (10772480, 0, 0)
> >
> > 13:20:39.754068 - EVENT MANAGER: 
> > object:property-change:accessible-value for [DEAD] in [DEAD] (0, 0, 0)
> >
> > That suggest that Pluma may have gone completely non-responsive (as 
> > far as AT-SPI2 is concerned) and/or that AT-SPI2 is completely 
> > unhappy. Not sure which, but that's not an Orca bug. All I can do in 
> > Orca is try to discard these events as quickly as possible.
> >
> >
> >
> >
> > On 3/14/20 13:12, Alex ARNAUD via orca-list wrote:
> > > Le 14/03/2020 à 18:06, Joanmarie Diggs a écrit :
> > > > Confirmed. Orca is getting flooded by insanely large text insertion 
> > > > events. I'll see if I catch that condition and eliminate it. Thanks 
> > > > for the report! 
> > > Is it a GTK issue or a more general one?
> > >
> > > Best regards.
> > >
> > > _______________________________________________
> > > orca-list mailing list
> > > orca-list gnome org
> > > https://mail.gnome.org/mailman/listinfo/orca-list
> > > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > > Orca documentation: https://help.gnome.org/users/orca/stable/
> > > GNOME Universal Access guide: 
> > > https://help.gnome.org/users/gnome-help/stable/a11y.html
> >
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > Orca documentation: https://help.gnome.org/users/orca/stable/
> > GNOME Universal Access guide: 
> > https://help.gnome.org/users/gnome-help/stable/a11y.html
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: 
> https://help.gnome.org/users/gnome-help/stable/a11y.html