Komodo 11 unresponsive and spawing lots of processes on the server

I don’t know if the two things mentioned above are related, however:

I use Komodo to work on files stored on a “remote” server. The server is not really remote as it is in my very same office. Since I installed Komodo IDE 11 I have barely been able to work with it due to constant freezing for some seconds. In the past I have had this problem when working really remotely and on a slow and lagging internet connection, however I don’t believe this can be the problem this time as my laptop is wired to the server (no wifi). I have changed the cable to the server with no apparent effect.

Trying to find some kind of reason I looked at what happened on the server and at least I don’t think it is normal the amount of processes that it spawns. The ones shown below are only 1/13th of the real amount:
root 30058 0.0 0.6 11460 6440 ? Ss 20:45 0:00 sshd: root@notty
root 30059 0.0 0.6 11460 6412 ? Ss 20:45 0:00 sshd: root@notty
root 30060 0.0 0.6 11460 6440 ? Ss 20:45 0:00 sshd: root@notty
root 30061 0.0 0.6 11460 6472 ? Ss 20:45 0:00 sshd: root@notty
root 30062 0.0 0.6 11460 6488 ? Ss 20:45 0:00 sshd: root@notty
root 30063 0.0 0.6 11460 6460 ? Ss 20:45 0:00 sshd: root@notty
root 30065 0.0 0.6 11460 6488 ? Ss 20:45 0:00 sshd: root@notty
root 30066 0.0 0.6 11460 6440 ? Ss 20:45 0:00 sshd: root@notty
root 30067 0.0 0.6 11460 6488 ? Ss 20:45 0:00 sshd: root@notty
root 30091 0.0 0.1 2580 1808 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30168 0.0 0.1 2580 1732 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30169 0.0 0.1 2580 1820 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30170 0.0 0.1 2580 1640 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30171 0.0 0.1 2580 1596 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30172 0.0 0.1 2580 1652 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30173 0.0 0.1 2580 1724 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30174 0.0 0.1 2580 1812 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30175 0.0 0.1 2580 1664 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30176 0.0 0.1 2580 1660 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30177 0.0 0.1 2580 1820 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30178 0.0 0.1 2580 1752 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30179 0.0 0.1 2580 1528 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30180 0.0 0.1 2580 1820 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30181 0.0 0.1 2580 1644 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30182 0.0 0.1 2580 1596 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30183 0.0 0.1 2580 1640 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30184 0.0 0.1 2580 1764 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30185 0.0 0.1 2580 1636 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server
root 30186 0.0 0.1 2580 1576 ? Ss 20:45 0:00 /usr/lib/openssh/sftp-server

also every now and then it pops up the login window (even 2 or 3 one above the other), but I don’t need to log in, I can just dismiss them with “cancel” and can go on working.

@tribis, is this an upgrade server config or is a new one you setup in Komodo 11?

Could you try checking if those processes on your “remote” machine are match to a degree by processes on your local? It sounds like you might be experiencing a reported:

  • Carey

It is an upgraded configuration.
Looking at the joblist it looks like there is only one subprocess for the file that is currently focused. When I focus on a different file the label of the subprocess changes to that filepath.

@tribis, could you see if using this connect in Safe Mode results in the same issue?
Help > Troublelshooting > Restart in Safe-Mode.

It seems like this solves the problem:
No freezing or lagging whatsoever. I have opened approx 15 files as usual but only two processes are to be seen on the server.
Previously I had at least 1 sftp process for each file opened and the sequence of processes was repeated for a random time (increasing and decreasing the same sequence of processes in unpredictable ways).

However this time I could not connect at first, I had to create a new sftp server and re-add folders to my project. When I double-clicked on the original folders to view and open files I could not log to the server with the provided login. Maybe because it is not sftp. The result is that I have double folders: the one that originally was in the project and the one that I had to add to be able to use them.

hmm, I see now it is re-using the old sftp connection, so I don’t know why it can’t connect.
and having re-started a new safe-session I see that I cannot even connect to the previously added directory (the one added in safe-mode). So this can only be an emergency solution, nothing that I can use regularly.

Ok, I would workaround the issue by reverting back to the non Safe-Mode (restart Komodo normally) then re-create the connections in your server prefs and re-add your folders to your project. I realize that is a pain and I apologize for that. You’ve provided helpful information that I think relates back to the issue I shared above though.

I have created a new project (currently two folders in it) that I have connected to the server using a newly created SFTP connection. I have not deleted the old ones yet.
I have only opened files from that connection.

The lagging and freezing is over (only a minor lagging when switching tab) and login dialog popping up has also not happened yet. I must say that this bettering had already taken place after the first time I ran in normal mode subsequent to a first run in safe-mode (can’t say of course whether it has something to do with it).

However looking at the server processes there has been no change: I still have 12-13 blocks of 9-12 sftp-processes:

I’m happy that now it is possible to work and cross my finger that it will last.

@tribis, I can’t say whether or not those connections are because of Komodo or not. It’s a fair guess but that’s not really something we can work with. I’ll add these details to the ticket above. There isn’t much more to be done here I don’t think. Next step will be digging into and resolving this ticket:

OK, thank you.

No problem! Thanks for reporting and your continuing to use Komodo @tribis!

Just wanted to add my 2 Cents on this topic for some additional infos: It seems like Komodo is re-creating connections till the limit is reached so a connection from a third party program is no more possible (connection limit reached).

Another thing related to remote connections is that changes are not displayed in the file-browser. That would not be a problem if there is a “refresh button” or something similar but there isn’t. So i have to log in with an ftp program, grab the name of the file and open it manually in komodo with typing the complete filename…thats really bad.

@petewulf If I understand correctly the point about the refresh button, I can say that there is a “Refresh Status” item in the context menu, by right clicking on any folder.

In my case it always is greyed out (I should report this as a separate issue), but I can use the shortcut Ctrl+K, R, that should do.

I can also say this. But if you’re seeing a bug @petewulf let us know. We’v
e had issues with that menu item.

That sounds like a reasonable guess. Thanks for chiming in. I originally thought no one else was hitting this (other than @babobski, the original reporter) but it looks like it was perhaps hard to see.