Description of problem: cpu utilization goes to 50% Version-Release number of selected component (if applicable): yelp 3.14.1 How reproducible: I think excessive cpu is consumed after any search. Steps to Reproduce: 1.start yelp from command line # fyi: same problem with just yelp and no --display. me $ yelp --display=:1 ** (yelp:10725): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (yelp:10725): Gtk-WARNING **: Symbolic icon yelp-bookmark-remove-symbolic-ltr of size 16 is in an icon theme directory of size 128 openjdk version "1.8.0_25" OpenJDK Runtime Environment (build 1.8.0_25-b18) OpenJDK Server VM (build 25.25-b02, mixed mode) 2.click on magnifying glass to do searched. 3.I entered the search term: toggle 4.quit yelp to get back cpu time. Actual results: Noticed cpu utilization going to 50%. I am on a dual processor laptop. ps -aux | grep yelp me 10725 95.4 4.8 339612 98720 pts/0 Rl+ 16:56 8:22 yelp --display=:1 me 10918 0.0 0.1 5084 2260 pts/1 S+ 17:05 0:00 grep yelp me $ Expected results: Additional info:
Start up yelp from command line or by clicking on some help icon in some other product. for instance, gnome-terminal. Click on the search icon in yelp. Type in a query, like: toggle press enter to initiate search. CPU utilization increases to almost 100% on one of my two processors or 50% overall.
Similar on F22 for me. Steps to reproduce: 1) $ yelp 2) search toggle 3) exit 4) cpu 100% ↪ yelp --version yelp 3.16.1
Created attachment 1085957 [details] A backtrace from gdb attached to yelp while being busy Steps to reproduce: 1. open yelp 2. press the search button in GtkHeaderBar 3. search for "glade" (without quotation marks) 4. close yelp What should happen: The yelp process should exit after some time. What happens: yelp process is running at 100% CPU on one core Affected version: yelp-3.16.1-1.fc22.x86_64 gtk3-3.16.7-1.fc22.x86_64 glib2-2.44.1-2.fc22.x86_64 Additional info: see attached backtrace
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still present on F23. Please change the bug metadata.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Since nobody seemed to care to set the version to F23 I opened a new bug for this on https://bugzilla.redhat.com/show_bug.cgi?id=1287818