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 432685 - Using brltty can consume all the CPU
Using brltty can consume all the CPU
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: braille
unspecified
Other All
: Normal normal
: ---
Assigned To: Willie Walker
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-23 17:08 UTC by Willie Walker
Modified: 2007-05-03 17:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to put an IO on the BrlAPI file descriptor instead of polling on gidle (2.34 KB, patch)
2007-05-02 16:33 UTC, Willie Walker 		committed Details | Review

Description Willie Walker 2007-04-23 17:08:25 UTC 
When brltty is in use with Orca, we notice that the CPU usage of Orca can go towards 100%.  The reason for this is that we're polling BrlAPI for braille input events via a gidle handler. 

In discussions with the BrlAPI maintainers, the recommendation for handling braille input events is to turn this into a callback mechanism versus a polling mechanism:

gobject.io_add_watch(b.fileDescriptor, gobject.IO_IN, f, args...)

See als http://www.pygtk.org/pygtk2tutorial/ch-TimeoutsIOAndIdleFunctions.html
Comment 1 Willie Walker 2007-05-02 16:33:18 UTC 
Created attachment 87399 [details] [review]
Patch to put an IO on the BrlAPI file descriptor instead of polling on gidle
Comment 2 Mike Pedersen 2007-05-03 15:44:14 UTC 
Hermann on the list has reported that he is nolonger seeing this problem.  I'm also testing with the latest and not noticing any problems.  I think this one is OK to close.
Comment 3 Willie Walker 2007-05-03 17:02:21 UTC 
Thanks.  Closing as FIXED.