Getting weird issue where Komodo is not responding after turning back on the monitor

My configuration is a laptop plugged into a monitor, the monitor has a higher resolution. As of 9.3.1, when I come back to my computer and turn on the monitor, Komodo freezes up using 25% of the CPU. It then seems like it is trying to redraw itself and then fails after redrawing the scroll bars. It also keeps opening up some kind of dialog or something. And that dialog keeps appearing and disappearing so my bottom windows bar keeps jumping. I quickly took a screenshot.

This happened 2X already so far. The first time I let it run for a few hours with no luck and killed Komodo. The 2nd time, I wanted to see if I could catch the dialog itself quickly, so I clicked “show desktop” to see if the dialog shows up (It is not uncommon for Komodo to have dialogs show up behind everything, same happens when I reopen my remote workspaces, the dialogs get caught behind the window and I have to hide the other windows). Show Desktop fails to work for some reason, so I manually hid all the windows. And somehow my Komodo instance returned back to normal instead of showing a dialog.

(I did not experience this in 9.2.X and I don’t think I did in 9.3 either, but I had 9.3 for shorter time) )

Here is my error log:

[2015-12-09 12:58:33,592] [ERROR] koSFTPConnection: SFTP do_openSocket ERROR: A socket operation was attempted to an unreachable host
[2015-12-09 12:58:33,780] [ERROR] console-logger: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [koIRemoteConnectionService.getConnectionUsingUri] (2) in chrome://breadcrumbs/content/breadcrumbs.js:1461
Traceback (most recent call last):
  File "chrome://breadcrumbs/content/breadcrumbs.js", line 1461, in 

    [2015-12-09 12:58:35,839] [WARNING] console-logger: Key event not available on GTK2: key="u" modifiers="control,shift" (1) in chrome://komodo/content/komodo.xul:0
    [2015-12-09 12:58:35,845] [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-12-09 21:23:54,594] [WARNING] console-logger: Error in parsing value for 'opacity'.  Declaration dropped. (1) in chrome://komodo/skin/images/toolbox/snippet.svg?preset=hud:0
    [2015-12-10 01:23:19,312] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'multiple_caret_area'
    [2015-12-10 01:23:19,313] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_4'
    [2015-12-10 01:23:19,313] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_5'
    [2015-12-10 01:23:19,315] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_2'
    [2015-12-10 01:23:19,315] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_3'
    [2015-12-10 01:23:19,316] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_1'
    [2015-12-10 01:23:19,318] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_change'
    [2015-12-10 01:23:19,318] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_local_change'

Could you see if these steps resolve your issue?

http://docs.komodoide.com/Troubleshooting/Komodo-has-weird-graphical-artifacts

Alright, I made the change. Once I get around to restarting Komodo, I’ll see if it makes a difference.

Though I should note the issue I had happens randomly. (not every time I turn on the monitor). So during say 3 weeks that Komodo 9.3.1 has been out, this happened 2X.

Alright so it has been 2 weeks later, and I still got that issue after the change to the settings.

And again hiding seems to solve the issue. (The issue happened on the 24th, the 23rd is just extra exception I saw and decided to include it if it might be another issue or not, not sure)

[2015-12-23 21:50:30,967] [ERROR] commands: An error occurred executing the cmd_startIncrementalSearch command
-- EXCEPTION START --
[Exception... "[JavaScript Error: "this._view is null" {file: "chrome://komodo/content/library/findController.js" line: 415}]'[JavaScript Error: "this._view is null" {file: "chrome://komodo/content/library/findController.js" line: 415}]' when calling method: [nsIController::doCommand]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: chrome://komodo/content/library/commands.js :: command_doCommand :: line 263"  data: yes]
+ QueryInterface (function) 3 lines
+ message (string) '[JavaScript Error: "this._view is null" {file: "chrome://komodo/content/library/findController.js" l'...270 chars
+ result (number) 2153185313
+ name (string) 'NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS'
+ filename (string) 'chrome://komodo/content/library/commands.js'
+ lineNumber (number) 263
+ columnNumber (number) 0
+ location (object) JS frame :: chrome://komodo/content/library/commands.js :: command_doCommand :: line 263
| + QueryInterface (function) 3 lines
| + language (number) 2
| + languageName (string) 'JavaScript'
| + filename (string) 'chrome://komodo/content/library/commands.js'
| + name (string) 'command_doCommand'
| + lineNumber (number) 263
| + columnNumber (number) 0
| + sourceLine (string) ''
| + caller (object) JS frame :: chrome://komodo/content/library/commands.js :: command_doCommandAsync :: line 215
| + formattedStack (string) 'command_doCommand@chrome://komodo/content/library/commands.js:263:0
command_doCommandAsync@chrome://'...476 chars
| + inner (object) null
| + data (object) [xpconnect wrapped nsISupports]
| + QueryInterface (function) 3 lines
| + initialize (function) 3 lines
-- EXCEPTION END --
[2015-12-23 21:50:30,967] [ERROR] keybindings: 
-- EXCEPTION START --
2147500037
+ 0 (number) 2147500037
-- EXCEPTION END --
[2015-12-23 21:50:31,000] [ERROR] console-logger: TypeError: this._view is null (2) in chrome://komodo/content/library/findController.js:415
Traceback (most recent call last):
  File "chrome://komodo/content/library/findController.js", line 415, in 

[2015-12-24 07:34:19,296] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'multiple_caret_area'
[2015-12-24 07:34:19,298] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_4'
[2015-12-24 07:34:19,299] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_5'
[2015-12-24 07:34:19,299] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_2'
[2015-12-24 07:34:19,299] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_3'
[2015-12-24 07:34:19,302] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_cursor_1'
[2015-12-24 07:34:19,305] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_remote_change'
[2015-12-24 07:34:19,305] [WARNING] koScintillaSchemeService: applyScheme:: no indicator for name 'collab_local_change'

Thanks for the information. Our devs will follow up when they get back from holiday.

At this point I would recommend you reset your profile, as it’s very hard to tell exactly what is going on. To reset your profile hit Help > Troubleshooting > Reset Everything.

Will that kill my workspaces and open files?

Yes, unfortunately. It resets Komodo to the way it was when you first installed it.

I have not gotten around to starting from scratch since starting my workspace from scratch is far more work than it being reset once every few weeks. But after a while I think the source of this is tied down to redrawing the UI when it resizes resolutions.

After 9.3 I did a change.

My laptop only has a DVI port and VGA port. So I used a DVI->HDMI adapter. I later switched to a DVI cable with no adapter. When I did that, when I turned on the screen, Windows did a resolution rescale like animation for a second.(Probably accounting for difference between my native 1920x1080 resolution and my 21:9 widescreen monitor). This resolution resizing is most likely what triggers this issue. I went back to DVI adapter -> HDMI and so far it seems to be good so far.