GNOME Bugzilla – Bug 512108
saving with gedit uses a great amount of cpu
Last modified: 2008-03-30 16:07:46 UTC
Please describe the problem: gedit seems to use an insane amout of cpu each time you save a document. I'd like to know if there is a specific reason for that. I mean, if I actually *noticed* a global performance hit evertime gedit saves, there must surely be some hidden monster that needs optimization in the code? Steps to reproduce: 1. open a plain text file in gedit and bluefish* 2. make some modifications in them 3. save in gedit 4. save in bluefish my documents typically have 9000 characters (1500 words) and weigh <10 KiB. This is not taking into account documents that need syntax highlighting such as html or python files. Actual results: gedit shows a big cpu usage for about 2-5 seconds (according to the sys monitor applet and my cpu fan), whereas bluefish does not Expected results: do not use a lot of cpu, or at least don't make my computer lag behind when I am typing :) Does this happen every time? yes Other information: I use autosave (this happens even without it), I have pentium M processors (>1.7 Ghz) and plenty of ram.
sorry, the * after "bluefish" was just there as a footnote for the paragraph that followed ("my documents typically have 9000 characters (1500 words) and weigh <10 KiB. This is not taking into account documents that need syntax highlighting such ashtml or python [...]")
we figured out on irc that this was due to the huge .recently-used.xbel. *** This bug has been marked as a duplicate of 488507 ***