After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 576954 - Accerciser takes a lot of CPU when idle
Accerciser takes a lot of CPU when idle
Status: RESOLVED OBSOLETE
Product: pyatspi2
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-03-27 13:20 UTC by Eitan Isaacson
Modified: 2019-03-27 20:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This is the original powertop result my notebook (Toshiba Satelite L300-144). (4.57 KB, text/plain)
2009-04-30 10:06 UTC, Hammer Attila
Details
This is the second powertop result, see my comment below. (3.67 KB, text/plain)
2009-04-30 10:11 UTC, Hammer Attila
Details
This is the third powertop result, see my comment below. (4.43 KB, text/plain)
2009-04-30 10:19 UTC, Hammer Attila
Details

Description Eitan Isaacson 2009-03-27 13:20:24 UTC
When I launch accerciser and it just sits there, it takes about %50 of the CPU.
Comment 1 Hammer Attila 2009-04-30 10:06:27 UTC
Created attachment 133641 [details]
This is the original powertop result my notebook (Toshiba Satelite L300-144).

This is the original powertop result my notebook (Toshiba Satelite L300-144). Now I don't doing modification with at-spi and orca source tree.
Comment 2 Hammer Attila 2009-04-30 10:11:37 UTC
Created attachment 133642 [details]
This is the second powertop result, see my comment below.

This is the second powertop result after I doed the following modification:
In src/orca/orca.py module, I changed the line "registry.start()" to
 "registry.start(gil=False)
Interesting, but after doed this modification, my notebook does'nt produce a disturb beep every time when disk usage or large task happen. This is fantastic!

Attila
Comment 3 Hammer Attila 2009-04-30 10:19:27 UTC
Created attachment 133645 [details]
This is the third powertop result, see my comment below.

Sure by sure, I doed second suggestion with pyatspi/registry.py:
time.sleep(1e-3)

Interesting, but when all modifications doed, the cpu usage is very low: Now 1. cpu is 6.5%, 2. cpu is 9.8%. This is an Intel Dualcore T2370 processor, and now I using 32 bit of Jaunty.

Very fantastic. I don't known change or not change my notebook battery time, because now charging after second powertop look.

Will, I have some questions, I would like do this two modifications with patches:
1. Orca and at-spi uses now only the git repository?
2. If yes, how can make the patch, similar with svn diff >patch.txt? I
try git diff >patch.txt, but the patch -p0 <patch.txt does'nt work.
3. I use 2-26 or trunk age when I do this two patch?

Attila
Comment 4 Eitan Isaacson 2009-04-30 11:55:59 UTC
Hi Hammer,

This is excellent news! Yes, git is very easy to use, and it is similar to SVN for making patches. We would welcome those two changes once you provide patches.

Comment 5 Willie Walker 2009-04-30 13:44:45 UTC
Eitan - is the GIL code necessary?  I remember doing it in the Orca atspi code because I was chasing down nasty hangs, but I believe I eventually found the culprit of those hangs was bad threading code in DECtalk.  So, if the GIL code is not necessary, maybe we could make the default for the 'gil' parameter be 'False' in pyatspi.registry.start?

Alternatively, I could add an option to Orca (and you could do something similar in Accerciser) to allow the user to override the value as a means to experiment.
Comment 6 Eitan Isaacson 2009-04-30 14:09:01 UTC
It is necessary for multi-threaded apps, i think.

I agree that 'gil' should False by default. But it constitutes as a API change, so I would not do that in a stable release. On the other hand gil=False in accerciser and orca would be a good idea for the next point release.

Comment 7 André Klapper 2012-02-26 10:41:43 UTC
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". 
Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports.

IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
Comment 8 André Klapper 2013-08-14 10:04:35 UTC
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Comment 9 Magdalen Berns (irc magpie) 2014-11-14 23:24:08 UTC
I'm going to go ahead and close this because it concerns a very old version.
Feel free to open a new bug if the problem persists.