On 08/31/2009 02:43 PM, Myk Melez wrote:
>  Yeah, I checked pystderr.log and pystdout.log after experiencing the 
>  problem, but they were empty. :-/
This just happened again after I'd unchecked "Check for status changes 
from outside of Komodo" and restarted Komodo. So I checked the log files 
again, and this time there were three exceptions in pystderr.log:

>  [2009-08-31 15:00:32,171] [ERROR] koCodeIntel: error evaluating 
>  completions:
>    trigger: <Trigger 'python-complete-object-members' at 11967>
>  ...
>  [2009-08-31 15:00:32,634] [ERROR] koCodeIntel: error evaluating calltip:
>    trigger: <Trigger 'python-calltip-call-signature' at 11972>
>  ...
>  [2009-08-31 15:02:01,263] [ERROR] koCodeIntel: error evaluating 
>  completions:
>    trigger: <Trigger 'python-complete-object-members' at 12736>
>  ...

After I shut down Komodo, pystderr.log included mention of two 
additional errors in the KoObserverService and a bunch of warnings about 
observers not being removed.

After I restarted Komodo, it started out using about 85MB resident 
memory, which is normal, but right from the start only the first 
version-controlled file tab had an icon. And about a minute later 
Komodo's memory usage climbed rapidly, reaching 300-400MB within a 
couple dozen seconds. Yet pystderr.log remained empty.

I'm now running Komodo with Mercurial integration completely disabled to 
see if that has any effect on the problem.

-myk

_______________________________________________
Komodo-beta mailing list
Komodo-beta@[...].com
http://listserv.ActiveState.com/mailman/listinfo/komodo-beta