[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#859262: Re: freezes Orca screen reader



So I just handled the value-related "The process appears to be hung"
exception. I saw that you also had the name-related exception. But the
line number suggests to me that you don't have another change I made,
namely to return immediately in isLayoutOnly() if obj is dead. I'm not
positive, but I'm hopeful that check will prevent the name-related
exception. (And if not, I'd like to know that.)

Therefore, before you try to log other issues, would you mind pulling
master or the gnome-3-24 branch so you have the latest?

Thanks again!
--joanie

On 04/28/2017 03:08 PM, Paul Gevers wrote:
> Hi,
> 
> On 23-04-17 19:27, Paul Gevers wrote:
>> On 23-04-17 15:32, Joanmarie Diggs wrote:
>>> That segfault is an AT-SPI2 bug. And apparently an elusive one.
>>> https://bugzilla.gnome.org/show_bug.cgi?id=767074
>>
>> Just to get things straight, do you mean here that you do or that you
>> don't believe this segfault has anything to do with the current bug?
> 
> Pending an answer :)
> 
>> If not, I can try getting logs until I am not hit by this segfault AND
>> there is something more in the log than the already known issue.
> 
> Not sure if there is anything interesting in the log, but I have a new
> one where orca didn't crash. Does that help?
> 
> Paul
> 


Reply to: