gedit won't exit and consumes 100% CPU

[Eric Morgan]

Binary package hint: gedit

Start gedit and do nothing.
Quit gedit
check top and gedit is still in memory at at 200% CPU and system heats up.
Kill gedit (with kill or from system monitor)
CPU drops to normal levels.

Let me know if you want more logs/info

This bug is a potential system damage bug if fans in laptops and such can't keep up with a 100% duty cycle for extended periods.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gedit 2.30.0git20100413-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue May 4 10:06:39 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gedit

[Pedro Villavicencio (pedro)]

Thanks for the report, please try to obtain a backtrace of the hang following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[TecnoBrat (tecnobrat)]

@nowhere do you use the ubuntu-on-rails ppa by any chance? I am having the same issue, but I haven't investigated enough yet.

[TecnoBrat (tecnobrat)]

Backtrace using gdb

[Eric Morgan (gemorgan)]

I don't use that ppa. And I haven't had a chance to run the backtrace
yet but should be able to work it in today.

On May 5, 2010, at 9:44 AM, TecnoBrat <email address hidden> wrote:

> @nowhere do you use the ubuntu-on-rails ppa by any chance? I am
> having
> the same issue, but I haven't investigated enough yet.
>
> --
> gedit won't exit and consumes 100% CPU
> https://bugs.launchpad.net/bugs/575278
> You received this bug notification because you are a direct subscriber
> of the bug.

[David Franklin (dpf1)]

Same issue here. Gedit process stays active in memory and each subsequent opening of gedit adds another process. I stumbled upon it when shutting down and was prompted if I wanted to exit all existing programs first. Eight instances of gedit were running while none had a window open.

[talent03 (talent03)]

I just encountered this problem using gedit and the gedit gmate repo. I also had this problem with the autocomplete plugin. Buggy plugins seem to cause this for me. Gedit on its own is not a problem.

[Eric Morgan (gemorgan)]

Here's my backtrace. Let me know if we need some more in it...

[Eric Morgan (gemorgan)]

BTW I didn't think twice ten minutes ago about about viewing a text file and quiting gedit. I few minutes later I could feel the heat blowing on me from the across my cube, checked and the CPU temp was 97C...

[Eric Morgan (gemorgan)]

I confirm that disabling ALL plugins did NOT stop the runaway problem. However, completely removing the gedit-plugins package did stop the problem from occuring. When quitting gedit with all plugins disabled and the gedit-plugins package removed, the CPU usage spikes briefly to 200% on my system then falls off when gedit exits.

Reinstalling the gedit-plugins package did NOT bring the problem back alone, even tho it enables some plugins by default upon install. Snippets is fine too. I'll have to go down the list of plugins to find the offending one...

[Launchpad Janitor (janitor)]

[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]

[Vincent Pottier (vpottier)]

On gedit 2.30.3
I've got the same problem. I had to kill the process. (Sometimes twice when I reopened Gedit before I killed it).
I have removed the plugin folder, and re-installed them one by one.
There is no more problem of CPU. Mysterious

The (French, i'm affraid) list of my plugins :
(0|1 : the plugin was unactived|active)
1 Advanced Bookmarks
0 Afficher/Masquer la barre d'onglets
1 Align
0 Chiffrement de texte
1 Class Browser
0 Commander
1 Commentateur de code
0 Complétion de mots
1 Complétion de parenthèses
1 Console Python
0 Édition multiple
1 Enregistreur de session
1 Espaces intelligents
1 Extraits de code
1 Find in files
1 Find Open
0 Function browser
1 Gedit Open File
0 Gemini
0 Go to File
1 Indicateur d'espaces
1 Insérer la date et l'heure
0 Joindre/couper les lignes
0 Liste des balises
1 Modificateur
1 Modifier la casse
1 Multi-Edit
0 Outils externes
1 Ouverture rapide
1 Panneau du navigateur de fichiers
0 Pastie
0 Prise en chage de Devhelp
1 Quick Highlight Mode
0 Rail Extract partial
0 Rail File Loader
0 Rail Hot Commands
0 Rail Hotkeys
1 Regex Search and Replace
0 Save without trailing space
1 Sélecteur de couleurs
1 Signets
1 Simple Folding
1 Smart Indent
1 Snap open
1 Statistiques du document
1 Tabme de caractères
1 TabSwitch
0 Terminal intégré
1 Text Tools
1 TODO List
1 Trier
1 Vérification orthographique
0 Word completion
1 Zen Coding

[Vadim Rutkovsky (roignac)]

Is this still reproducible? Can someone affected attach strace log (see https://wiki.ubuntu.com/Strace) or even point at the faulty plugin?

[Eric Dalquist (eric-dalquist)]

I'm not sure it was the same issue but I was having a problem where opening gedit would result in 100% CPU usage. I started gedit with strace and quickly realized my problem. I had previously opened a few files in a directory that contains about 65000 files:

edalquist@bohemia:~$ history |grep export/layout | grep gedit
 1956 gedit /home/edalquist/JavaClasses/workspace_37/UW_uPortal-HEAD/export/layout/lgkonrad.layout
 1957 gedit /home/edalquist/JavaClasses/workspace_37/UW_uPortal-HEAD/export/layout/cmnguyen2.layout
 1958 gedit /home/edalquist/JavaClasses/workspace_37/UW_uPortal-HEAD/export/layout/portal.user2.layout

Looking at strace it appears that gedit is scanning all of the files in the /home/edalquist/JavaClasses/workspace_37/UW_uPortal-HEAD/export/layout directory.

I renamed /home/edalquist/JavaClasses/workspace_37/UW_uPortal-HEAD/export to /home/edalquist/JavaClasses/workspace_37/UW_uPortal-HEAD/export_temp and now gedit opens just fine.

Again not sure if this was the same issue but I figured more info is always helpful

[David Császár (p5)]

Just observed the problem described by Eric. I had previously opened a file in a directory with 82359 entries.

[Paul White (paulw2u)]

Eric (and anyone else affected),

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and GNOME since that time.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

[Launchpad Janitor (janitor)]

[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]