Closed GoogleCodeExporter closed 8 years ago
Hi,
Are you running on a 32 or 64 bit platform?
Please run Editra in profiler mode (Editra -p) and let it sit till this is
happening
then send me the output file (editra.prof). This should make it possible to see
what
is eating the cpu.
Please also include a list of any plugins you have installed and whether it
matters
what kind of file is open or not.
Thanks!
Cody
Original comment by CodyPrec...@gmail.com
on 27 Jan 2010 at 3:25
I'm running on an amd64 machine.
I have the following plugins enabled: Calculator (0.6), CodeBrowser (0.9),
FileBrowser (1.5), MacroLauncher (0.1), Projects (1.5) and PyShell (0.8). Only
CodeBrower and Projects are visible in the window.
I tried with the svn version 5.33, and a .txt file open, and I didn't have 100%
cpu
usage, so it might have been fixed in the trunk, or it doesn't happen with .txt
files. I'll investigate more.
I'm attaching the profiler file with high cpu usage after a few hours. This is
with
the binary version 5.30, with a python file open. I can't open the profiler file
because I don't have python-profiler installed, but I'll try to install it.
Thanks,
EG
Original comment by gaudet.e...@gmail.com
on 28 Jan 2010 at 5:01
Attachments:
Thank you I will try to analyze the profile output sometime today and get back
to you
about it.
(runsnakerun is a nice program for looking at python profiler output.)
Thanks again,
Cody
Original comment by CodyPrec...@gmail.com
on 28 Jan 2010 at 5:12
Hi,
Nothing is immediately jumping out as a cause to this. I do see a larger than
expected number calls to the UpdateUI handling though. There have been some
changes
in svn head that should reduce the number of update ui calls being made. The
Settings->Lexers menu is now configurable and by default has only a few things
in it.
Previously there were 70~ items in it each with an update ui handler attached.
Will keep investigating though as most of the update ui time appears to have
been
spent else where.
Original comment by CodyPrec...@gmail.com
on 28 Jan 2010 at 7:53
I've been using 5.33 from svn for a week non-stop, and I don't see high cpu
usage
anymore.
I recommend closing this bug as fixed in 5.33.
Original comment by gaudet.e...@gmail.com
on 31 Jan 2010 at 6:21
Ok thanks for the info will close for now, if it returns let me know.
Cody
Original comment by CodyPrec...@gmail.com
on 31 Jan 2010 at 9:58
Original issue reported on code.google.com by
gaudet.e...@gmail.com
on 27 Jan 2010 at 2:39