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 698579 - external tools: continues to consume 100% CPU after tool is stopped
external tools: continues to consume 100% CPU after tool is stopped
Status: RESOLVED FIXED
Product: gedit-plugins
Classification: Other
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-22 15:01 UTC by Adam Dingle
Modified: 2019-03-23 20:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2013-04-22 15:01:51 UTC 
To see the problem:

1. Start System Monitor so you can watch process activity.
2. In gedit, run an external tool which will run for a while (for example, building gedit itself).
3. Press Stop to stop the tool.

In System Monitor you'll see that gedit continues to consume 100% CPU even after the tool is stopped.
Comment 1 Ignacio Casal Quinteiro (nacho) 2013-04-22 19:24:43 UTC 
Fixed. Please give us some feedback if it works for you too.
Comment 2 Adam Dingle 2013-04-22 21:01:22 UTC 
Seems fine now.  Thanks for the quick response on this!