GNOME Bugzilla – Bug 660218
When I launch Thunderbird in my Oneiric or Precise system, I experiencing slow responsiveness for Orca
Last modified: 2012-02-20 19:53:42 UTC
Dear Developers, I don't no why happening this problem, but if I run for example Thunderbird my Oneiric system with Terminal, I experiencing slow responsiveness with Orca screen reader. I attaching the debug.out file with perhaps help determining why happening this problem. Attila
I forgot wrote following informations: My Oneiric system I using now Orca 3.2.0 packaged version, and Thunderbird version is 7.0 (Ubuntu package version is 7.0+build1+nobinonly0-ubuntu1). The debug.out file is very big unfortunately, because I haven't got possibility kill Orca without I need switch console, because my system is entire unresponsive when I launched Thunderbird. I try making a smallest debug.out file. Attila
Created attachment 197545 [details] A relative compressed smallest debug.out file Ok, I doed following: 1. I restarted Orca with orca --replace --debug-file=debug.out command in GNOME Terminal. 2. I press ALT+F2 key combination, wrote thunderbird command and pressed Enter key. After this I wait, wait, wait... I think 40 second later Orca begin spokening Thunderbird application title. Thunderbird downloaded my new e-mails, but I impossible to jump next unread message. I waiting 20 second, and because I not experiencing responsiving my system, I switch console, and doing a sync command to flush the stored debug.out file and execute sudo reboot command. Because in one minute work the generated debug.out is bigger with 5 MB, I compressed the debug file with zip format. Attila
Created attachment 197546 [details] This screenshot showing resource informations before Thunderbird not running This problem is not depending what Orca modules I use, so this problem not depending if I using Orca only with speech, only with braille or both speech and braille. I will be attaching three screen shot. The first screenshot showing in the resource page how many percentage CPU capacity is used, how many the memory percentage used the system before Thunderbird not running. TThe second screenshot showing equals window, except Thunderbird is already running. The third attaching screenshot showing the running processes. Attila
Created attachment 197547 [details] Resource informations when Thunderbird running This screenshot showing system resource informations when Thunderbird is running.
Created attachment 197548 [details] Running processes when Thunderbird is running This screenshot showing running processes if Thunderbird already running.
My notebook is a relative fast machine. My machine have got an Intel Dualcore t2300 CPU with speed is 1,73 GHZ. My notebook containing builtin 2 GB memory, and I using Ubuntu Oneiric 32 bit. My other Linux system oldest 3.1.7 Thunderbird release for example doesn't producing similar issue. Attila
Unfortunately this issue are reproducable my Ubuntu Precise development system, Thunderbird version is 9.0~b3. Attila
Created attachment 202968 [details] This debug file I created with my Ubuntu precise system This debug.out file I created my Ubuntu Precise system. Showing any useful information the debug.out file to determine why happening this issue? Attila
Copy and paste from what I sent to the Orca list: ~~~~~~~~~~~~~~~~~~ Hey all. >> TOTAL PROCESSING TIME: 24.5515 > > what unit is this? if its seconds that's really suprising. Yeah, it's seconds. And looking at Attila's debug output there are over 10,000 lines (yes ten thousand!!!) of object:property-change:accessible-name getting queued up. One line per event. In other words, this is an epic event flood from Thunderbird or Gecko. I'm really not sure what I can do other than to ask Thunderbird/Gecko to just cut it out for pete's sake. Trev, are you still involved with Gecko development? If so it would be awesome if you could take a look at this. Take care. --joanie
I filed this Mozilla bug for the issue: https://bugzilla.mozilla.org/show_bug.cgi?id=708692
*** This bug has been marked as a duplicate of bug 665870 ***