Comment 17 for bug 367372

I'm on Lynx, running gedit 2.30.3. I started getting this problem a few weeks ago. I got rid of it somehow but it's back now.

Seeing the direction on this report page, I started testing the plug-ins. I had reinstalled gedit and probably dropped all extra plug-ins in the process. Switching off the plug-ins one after another, I found all would switch off easily, except for Bestandsverkennerspaneel, which took a long time to switch off. I don't know the English name (the plug-in info doesn't show a "standard name"), but the name translates to something like "File Explorer Panel".

Figuring that this was something file related, I started saving files from gedit with new names, exiting and launching in between. For the first five, I had not changes. The sixth file I did by launching from the shell with a new filename. At that point the processor usage dropped back to normal.

Considering this is file-exploring related, I wonder whether the fact that I'm editing files in multiple fifty thousand file directories might be causing problems. I've been editing files from a single such directory for years, but it's recent that I've had multiple such directories, and it's from that same time that I'm writing files back to overwrite files in such copies. I'm not saying that this is definitely the cause, but it might be worth having a look at.

I'll leave that plug-in switched of for now, but feel free to ask me to test.