# Komodo edit Unstable after upgrade

Hi,

Recently uninstalled version komodo edit 8.5 and installed komodo edit 9.1. It has so far been incredibly unstable and pretty much unusable. I have uninstalled and re-installed it twice but the errors persisted. By unstable I mean it will just randomly gives a popup saying “unexpectedly crash” and then closes the whole application. There seems to be no obvious pattern for what causes the crashes. It has happened multiple times whilst merely typing and very frequently whilst opening the properties for custom command.

I am running it on windows 8.1 , dell inspiron , intel core i5.

Please let me know what other details would help.

Hi @gowerc,

Please see the “Override The Profile Folder Location” section in this link and see if that helps with your issue.

Something most likely has become corrupted in your profile as this is not occurring for anyone else, on Windows, that I’m aware of.

• Carey

Hi,

I read that article and since un-installed komodo edit again. I then deleted the 2 folders
\AppData\Local\ActiveState
\AppData\Roaming\ActiveState

and I then re-installed it however the crashes still are occurring.

Below is a dump from my pystderr.log

Perhaps a clash with my already installed python interpreter ?

When Komodo crashes and the dialog appears, is it asking you to send a crash report? If it does can you please PM me the email address you use?

Is there something that indicates to you that your Python is conflicting? The code intel error in your logs (assuming that is what you’re referring to) suggests to me that you incorrectly reset your profile. Was Komodo stopped when you did it? You could also try starting Komodo from the commandline using KOMODO_USERDATADIR environmental variable to point to a temp folder. This would ensure that Komodow as starting with a perfectly clean profile.
It would look something like this:

> set KOMODO_USERDATADIR=c:\some\temp\path
> path\to\komodo.exe


Can you please try that and see if the issue remains?

• Carey

Hi Careyh,

Thanks for the advice unfortunatly it is still not working for me

Upon doing some simple edits and saving a file I got the same error message. This time I followed the windows debug through and got the following (not sure if it helps or not)

Below is a copy of pystderr.txt that was created on my desktop after the program crashed


[2015-07-19 11:09:20,592] [INFO] Startup: Welcome to Komodo Edit 9.1.0 build 15798 (platform win32-x86, running on Windows post2012Server version 6.3.9600)
[2015-07-19 11:09:20,592] [INFO] Startup: C:\Program Files (x86)\ActiveState Komodo Edit 9\lib\mozilla\komodo.exe built on Sat May 30 06:10:24 2015
[2015-07-19 11:09:23,273] [WARNING] console-logger: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create (1) in resource://gre/modules/Preferences.jsm:381
[2015-07-19 11:09:23,275] [WARNING] console-logger: Bootstrapped manifest not allowed to use 'component' directive. (1) in file:///C:/Program%20Files%20(x86)/ActiveState%20Komodo%20Edit%209/lib/mozilla/extensions/scope-files@activestate.com/components/component.manifest:1
[2015-07-19 11:09:23,276] [WARNING] console-logger: Bootstrapped manifest not allowed to use 'contract' directive. (1) in file:///C:/Program%20Files%20(x86)/ActiveState%20Komodo%20Edit%209/lib/mozilla/extensions/scope-files@activestate.com/components/component.manifest:2
[2015-07-19 11:09:23,276] [WARNING] console-logger: Bootstrapped manifest not allowed to use 'interfaces' directive. (1) in file:///C:/Program%20Files%20(x86)/ActiveState%20Komodo%20Edit%209/lib/mozilla/extensions/scope-files@activestate.com/components/component.manifest:3
[2015-07-19 11:09:23,641] [WARNING] root: ko.logging has been converted to a CommonJS module; use require("ko/logging") instead (since Komodo 9.0.0a1).
@chrome://komodo/content/komodo.js:48:1

[2015-07-19 11:09:24,177] [WARNING] console-logger: Unknown property 'border-radius-top-left'.  Declaration dropped. (1) in less://commando/skin/commando.less:19
[2015-07-19 11:09:24,177] [WARNING] console-logger: Unknown property 'border-radius-top-right'.  Declaration dropped. (1) in less://commando/skin/commando.less:20
[2015-07-19 11:09:25,798] [WARNING] console-logger: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create (1) in file:///C:/Program%20Files%20(x86)/ActiveState%20Komodo%20Edit%209/lib/mozilla/components/koamAddonManager.js:138

[2015-07-19 11:09:28,832] [DEBUG] places_js: waiting for document complete
[2015-07-19 11:09:29,226] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_4'
[2015-07-19 11:09:29,226] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_5'
[2015-07-19 11:09:29,226] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_2'
[2015-07-19 11:09:29,226] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_3'
[2015-07-19 11:09:29,229] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_1'
[2015-07-19 11:09:29,229] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_change'
[2015-07-19 11:09:29,229] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_local_change'
[2015-07-19 11:09:38,229] [WARNING] console-logger: Key event not available on GTK2: key="u" modifiers="control,shift" (1) in chrome://komodo/content/komodo.xul:0
[2015-07-19 11:09:38,230] [WARNING] console-logger: Key event not available on some keyboard layouts: key="v" modifiers="control,alt" (1) in chrome://komodo/content/komodo.xul:0
[2015-07-19 11:09:48,766] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_4'
[2015-07-19 11:09:48,766] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_5'
[2015-07-19 11:09:48,766] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_2'
[2015-07-19 11:09:48,766] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_3'
[2015-07-19 11:09:48,766] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_1'
[2015-07-19 11:09:48,767] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_change'
[2015-07-19 11:09:48,769] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_local_change'
[2015-07-19 11:10:04,726] [WARNING] koDocument: setting koDocument.codePage is DEPRECATED, hardwired to 65001 (unicode mode): 65001 ignored



Unfortunately we do not support this version of Windows. Please see the system requirements on our downloads page:

Hi Nathanr,

Can you please clarify what this number means?

I am currently running windows 8.1. Under your system requirements you claim you support windows 8 so I am quite confused.

How about this part of my comment? @nathanr is referring to the platform name at the top of your logs which makes it look like it’s Windows Server 2012. See below. I’m a little confused about that as well. Why is your platform called Server 2012?

Hi Careyh,

It does not offer to send a crash report. I have pm’d you my email address.

Could it be a clash with some other software I have installed ? Below is a list of none standard software I have on my laptop at the moment
XAMPP
Visual Studio 2013
python3
python2
sublime text 2
AVG
R + R studio
GIT + source tree
VMware Workstation v11

Hi Careyh,

For the love of me I can’t work out how to send a private message How do I do it ?

Hi Defman,

Thanks for your quick reply. Unfortunately I don’t appear to have that option.

I gave you a new trust level (basic user), you should able to PM Carey now.

Thanks Defman,

PM sent

Could you please comment on this @gowerc?

You could try disabling your AntiVIrus to see if that works around the issue, it might be triggering false positives.

Hi Nathanr,

That seems to have made a difference. It is no longer crashing to desktop. It is however still a bit slow and unresponsive at times. At one point I resized the window and everything went pure grey except the physical text editing panel.

Might try one last uninstall / reinstall before I pack it in

Given the platform Komodo is detecting and the fact that your AV made it crash outright I’d say you’re seeing issues that Komodo is not the root cause of. Consider cleaning up your system or even doing a clean install of a stable version of Windows.