gedit uses high CPU during start

Bug #292486 reported by Vish
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

hi,
Description: Ubuntu 8.10
Release: 8.10

gedit version> 2.24.0-0ubuntu1

when opening any file in gedit the cpu usage jumps to nearly 100% and takes a few seconds to start. after the file has opened the CPU usage drops to normal...

how do i prevent this high cpu usage?

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: fglrx
Package: gedit 2.24.0-0ubuntu1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gedit
Uname: Linux 2.6.27-7-generic i686

Tags: apport-bug
Revision history for this message
Vish (vish) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gedit:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Vish (vish) wrote :

sebastian bacher> since u think that my problem is different from this bug>
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/276094

https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/276094/comments/11 << ur comment

which u initially thought was similar i think u should consider this as a separate bug

i have a 1.66GHz DUO core, which i dont think is a slow CPU...

when i used ubuntu 8.04 the gedit used to open in 4-6 secs... almost instantaneously

now since i'v upgraded to 8.10 it takes 35-40 secs... before the gedit update it was around 30 secs...

 so the update[2.24.1-0ubuntu1] has increased the opening time... and worsened my bug

Revision history for this message
Vish (vish) wrote :

disabling the file browser plugin, was helpful... i have no problems now without the plugin...

this confirms that this is not the same bug... please consider this as a seperate bug and fix the file browser plugin...

Revision history for this message
Michael Kogan (michael-kogan) wrote :

I'm having exactly the same problem and the workaround has worked out in my case, too. Thanks for that and I want to enforce that this bug semms not to be a dublicate of #276094!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.