Well, there is this:
Traceback (most recent call last):
File "/home/jesse/Dropbox/leo-editor/leo/plugins/qtGui.py", line
4560, in timerCallBack
idleTimeHookHandler()
File "/home/jesse/Dropbox/leo-editor/leo/core/leoGlobals.py", line
2959, in idleTimeHookHandler
g.doHook("idle",c=c)
File "/home/jesse/Dropbox/leo-editor/leo/core/leoGlobals.py", line
3000, in doHook
if not g.app.config.use_plugins:
KeyboardInterrupt
(I was thinking you meant crashing tracebacks...)
On Mar 31, 8:11 am, Jesse Aldridge <[email protected]> wrote:
> I'm seeing the same problem. There's no traceback. Just 100% cpu.
> Well 50% in my case but I think that's because I have two
> processors...
>
> On Mar 31, 6:43 am, "Ville M. Vainio" <[email protected]> wrote:
>
> > On Tue, Mar 31, 2009 at 2:07 PM, zpcspm <[email protected]> wrote:
> > > It's something qt-related, because loading leo with tk GUI looks fine.
> > > The trunk update that introduced this happened very recently, during
> > > the last series of commits.
>
> > Press ctrl + c on the console that launched leo and watch the
> > tracebacks. It will give a good clue.
>
> > --
> > Ville M. Vainiohttp://tinyurl.com/vainio
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
