ActiveState Community

The log file is at
%HOME%/appinfo/roaming/activestate/komodo{ide,edit}//
host-/pystderr.log

An alternative is to start Komodo from the console in
verbose mode, and see if there are any error messages
when you try to open a file:

c> cd "C:\Program Files\ActiveState Komodo IDE 5"
c> komodo -v

If it still hangs, could you try setting the
KOMODO_USERDATADIR environment variable to point
to a directory you own, such as:

c> mkdir %HOME%\komodo-appdata
c> set KOMODO_USERDATADIR=%HOME%\komodo-appdata
c> "C:\Program Files\ActiveState Komodo IDE 5"\komodo

Looking forward to seeing if this works for you.

Regards,
Eric

I found the file then, but it was empty. Now it contains something, but I believe that it's for a session that was started after I had to kill IDE when it hang.

Perhaps, error logging could be improved so that log files would contain something useful for you to determine what happens when a problem occurs.

It hang again, and again the pystderr.log is of zero size. It it was writing something to it, it should've flushed the data. Persisting navigation history is a waste of computer resources, but ensuring that error information gets logged is important.

I agree with you that diagnostics should get written to the file,
but most likely the hanging bug happens unexpectedly, so nothing
is getting logged. Did you try running Komodo with a different
value for KOMODO_USERDATADIR ?

As for history, I personally find it very useful, but am also
re-evaluating it to figure out how to lighten its load.

Regards,
Eric

I'm having a similar problen on windows vista SP1 64bit with 5.2 beta 1.

After unistalling the 5.1 version and doing a clean install of 5.2 beta 1, it took about 10 minutes to start up. At the top of the IDE it says ActiveState Komodo IDE 5.2 (Not Responding) when it should give a message about loading, configuring or otherwise doing something. After 10 minutes it behaved as expected. The log files had no errors in them.

When I restarted it it only took 5 minutes. Its consuming a fixed amount of memory and 0 CPU so I must assume its just stalled in some way. My 5.1 version took forever to load also which is why I took a chance on 5.2 beta.

When I looked at the splash screen, it had a list of recent files and projects that were simply inaccessible. Even though I had unistalled everything it still had my prefs. After I deleted them and restarted Komodo. On restart Komodo installed the code intelligence db and everything was snappy.

My guess is that somewhere in the carryover from 5.1 user data was something that fooled Komodo into thinking the code intelligence db was installed.

In any event, backup your 2 prefs files in C:\Users\\AppData\Roaming\ActiveState\KomodoIDE\5.2 and see if that helps.

Also C:\Users\\AppData\Roaming\ActiveState\KomodoIDE\5.2 is not browseable on vista through the explorer. That is you cannot see the "AppData" directory so you must type in the path to see that the logs are there.

Did you try running Komodo with a different
value for KOMODO_USERDATADIR?

No, I didn't because Komodo was already using a directory I owned.