Re: [orca-list] firefox freezes accessibility support

["B. Henry" <burt1iband gmail com>]

I saw this a lot when I ran fx26 under xfce on arch-linux. It was not always firefox that grabbed 75-100% 
CPU, speech-dispatcher often was fighting for huge percentage of the processor. 
In a few cases I could "blindly" go to another page as I knew where a control was that was next in a familar 
process and things cleared up, but in most cases this of course was not an option open to me. I don't every 
remember things calming down to more normal usages, and I'd waiting more than five minutes before killing 
things sometimes. 
I could sometimes kill firefox with normal ^q or alt f4, but sometimes had to resort to killall, pkill or 
similar.
As much because of this as anything else I grabbed the oldest firefox in the arch rollback machine, fx23. 
I've asked a few places but not gotten any reply as to whether 24 has any advantages re accessability or 
anything else for that matter. I know that at least using orca 3.4.2 with Ubuntu precise firefox25 was 
problematic, so so far I've stuck with 23. And for the record I'm using orca 3.10.2 here with xfce/arch.
I may be able to reproduce one cpu spike event, but as I don't really have a test environment now I'd rather 
wait till I have more than one thing to test or at least have an idea as to what others think is a trigger 
for this behavior. 
Regards,
--
B.H.\
i  


On Fri, Feb 07, 2014 at 11:13:56AM +0100, Peter Vágner wrote:
> Hello,
> Occasionally while browsing the web using Firefox I experience a freeze. I
> haven't found a way on how to get more relevant info. What happens is that
> orca goes completelly silent and firefox does not respond to keyboard
> events. If I keep running Firefox open without me doing anything I can see
> the CPU usage increases hogging one of the cores. The only workaround I am
> aware of is to launch gnome terminal and kill firefox. Immediatelly as
> firefox gets killed orca functionality returns back and I can continue
> working like normal.
> I can't definitelly reproduce this it's why I haven't tryed to report it
> earlier. I think this is happening for quite some time, I think Firefox 25,
> Firefox 26 and Firefox 27 are affected. I haven't yet tested newer versions.
> Do you know if there is corresponding Mozilla bug open for this already?
>
> Greetings
>
> Peter
>
>
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp