Re: [orca-list] orca randomly segfaults when closing pluma text editor

[Joanmarie Diggs <jdiggs igalia com>]

Mike, I've seen the CPU problem when AT-SPI2 has crashed. A while back I
tried to handle that scenario in Orca. But something.... I forget what
now.... made that challenging. I'll take another look at that, but if
you have any suggestions (or better still patches) for dealing with
AT-SPI2 crashes gracefully, that would be great.

Thanks!
--joanie

On 05/18/2016 01:23 PM, Mike Gorse wrote:
> Hi all,
>
> For some reason, at least on my system, if orca crashes, then it does
> not exit. Instead, it goes into some sort of loop where it uses 100% of
> CPU time until it is killed. So people may be seeing either a loop in
> orca or a crash for which AT-SPI is probably to blame.
>
> If you are able to access the machine without orca (by using a console
> screen reader or SSHing in from another computer, etc), then it might
> also help to connect to Orca's process using gdb (running "pidof
> python3" or "ps ax |grep orca" should help you figure out which process
> to attach to) and capture a full backtrace, particularly if you see
> "program received signal 11: segmentation fault" or something similar
> while attaching. You may need to install debug packages for AT-SPI and
> glib/gobject (how to do that will vary from distro to distro).
>
> Thanks,
> -Mike
> _______________________________________________
> 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
> Log bugs and feature requests at http://bugzilla.gnome.org