Re: [orca-list] orca randomly segfaults when closing pluma text editor
- From: Mike Gorse <mgorse alum wpi edu>
- To: orca-list gnome org
- Subject: Re: [orca-list] orca randomly segfaults when closing pluma text editor
- Date: Wed, 18 May 2016 13:23:58 -0400 (EDT)
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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]