New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Komodo 10 crashing on startup after working with SFTP #2082

Closed
ElGrangar opened this Issue Oct 3, 2016 · 18 comments

Comments

Projects
None yet
5 participants
@ElGrangar

ElGrangar commented Oct 3, 2016

Short Summary

Komodo sometimes crashes on startup after working with remote folders. When this occurs it does this every subsequent try, can only be worked around by starting without an internet connection so that it catches the error.

Steps to Reproduce

Not sure, but it happened on both my old personal laptop as well as a brand new work laptop with clean windows install. Seemingly at random.

Expected results

The editor opens with previous open files restored

Actual results

The program crashes without an error report/message and gets terminated by windows.

Platform Information

Komodo Edit 10, Windows 10.0.14393

Additional Information

I connect to external folders over SFTP, with a private key that has a passphrase. Maybe it could have something to do with that? As it crashes it doesn't ask me to enter the passphrase (which is what should happen directly on startup as it connects)
Where can I find a log to supply with the report?

@ElGrangar ElGrangar changed the title from Komodo 10 crashing o to Komodo 10 crashing on startup after working with SFTP Oct 3, 2016

@Naatan

This comment has been minimized.

Member

Naatan commented Oct 3, 2016

Please share your error log after reproducing the issue and before restarting Komodo again.

http://docs.komodoide.com/Troubleshooting/Where-does-Komodo-keep-settings-data#where-does-komodo-log-errors

@ElGrangar

This comment has been minimized.

ElGrangar commented Oct 17, 2016

It happened again, error log:
pystderr.log.txt

@Naatan

This comment has been minimized.

Member

Naatan commented Oct 17, 2016

Can you uninstall the gitbranch extension? It's no longer required as the functionality is built-in to Komodo 10.1

Other than that I don't see anything in your log that looks wrong. Does the crash happen consistently or is it random?

@ElGrangar

This comment has been minimized.

ElGrangar commented Oct 17, 2016

Huh, I don't recall even installing such an extension as I work with Git CLI but I'll look into that.

It seems to happen at random, but as I said - once it happens it keeps happening until I start Komodo without an internet connection.

@Naatan

This comment has been minimized.

Member

Naatan commented Oct 17, 2016

When you have your next crash could you send your prefs.xml to support@activestate.com and reference this ticket?

For finding your prefs.xml: http://docs.komodoide.com/Troubleshooting/Where-does-Komodo-keep-settings-data

@LionelLaffineur

This comment has been minimized.

LionelLaffineur commented Oct 29, 2016

Dears,

I have the same problem every time I start Komodo Edit 10.1; I've attached my log file
pystderr.log.txt.

It is easy to reproduce as it happens every time starting Komodo after a remote server has been connected.

Thanks in advance for your help,
Lionel

@Naatan

This comment has been minimized.

Member

Naatan commented Oct 31, 2016

@LionelLaffineur Please see my previous post, the same would apply to anyone having this issue. Thank you!

@Naatan

This comment has been minimized.

Member

Naatan commented Nov 3, 2016

OTRS #57884

Thanks @RogierVelde !

@Naatan Naatan added this to the 10.2 milestone Nov 3, 2016

@Naatan Naatan modified the milestones: 11, 10.2 Feb 22, 2017

@koyae

This comment has been minimized.

koyae commented Feb 24, 2017

@Naatan I just upgraded from 8.5 to 10.2 and I am having this problem. For me, crashes are consistent on every startup of Komodo and occur with the Windows "KomodoEdit has stopped working" message, which appears 3 to 5 seconds after KomodoEdit opens. I also have an entry in the Servers list that uses a passworded SSH-key.

Platform: Windows 7 Enterprise

Footnote: the heading you linked to with http://docs.komodoide.com/Troubleshooting/Where-does-Komodo-keep-settings-data#where-does-komodo-log-errors does not exist, and I'm not seeing any pystderr.log anywhere on disk. Edit: I opened Komodo again so it would crash once more and it kicked out the desired file.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Feb 24, 2017

Footnote: the heading you linked to with [...] does not exist

@koyae, are you saying the link doesn't work or you can't find the path on your system? If it's the latter please share what path you're trying to use.

The link works fine for me and those paths are correct.

@koyae

This comment has been minimized.

koyae commented Feb 24, 2017

@cgchoffman
screen

No heading describing where to find error-dumps under Version:Latest.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Feb 24, 2017

@koyae. K, the webpage works. As I said, those paths are correct so please share the path your are trying to find.

@koyae

This comment has been minimized.

koyae commented Feb 24, 2017

@cgchoffman For comparison, here's Version:9's page. I was saying the current version is missing the heading which @Naatan was trying to link to:
screen2

With regards to the log-file itself in my case, I think Komodo just failed to create a dump the first time. After reopening it to let it crash again, the file's now appeared (find attached).
pystderr.zip

Sorry for any confusion.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Feb 24, 2017

For comparison, here's Version:9's page. I was saying the current version is missing the heading which

Thanks for clarifying, I had no idea what your were talking about.

With regards to the log-file itself in my case, I think Komodo just failed to create a dump the first time. After reopening it to let it crash again, the file's now appeared (find attached).
pystderr.zip

That log file should always exist regardless of a crash. Komodo doesn't dump crash information to that file. It's just run time errors and information. See nathanr's comment here: #2082 (comment)

We're looking for prefs.xml files now.

Thanks for helping.

@koyae

This comment has been minimized.

koyae commented Feb 24, 2017

@cgchoffman I've sent a zipped version of my prefs.xml-file to the support@activestate.com address. Thanks and cheers.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Feb 24, 2017

I've sent a zipped version of my prefs.xml-file to the support@activestate.com address. Thanks and cheers.

@koyae awesome, thank you very much. I'm just about to start testing.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Feb 25, 2017

Thanks everyone. Reproduced this. The key was indeed the keys. Apologies that I didn't take a look at this sooner. Having said that, you'll have better luck using PuTTY on Windows for SSH work. If you're interested in switching to PuTTY we have docs for it and i'll be happy to assist you if you get stuck.

cgchoffman added a commit that referenced this issue Feb 27, 2017

Places: proxy key password to main thread. Fixes #2082
rn=

(integrated from the KomodoIDE 10.2.x branch change 2dbd364 by Carey Hoffman <cgchoffman@gmail.com>)

Komodo/KomodoIDE@2dbd364
@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Feb 27, 2017

There will be a nightly available with this fixed tomorrow 12 pm (Feb 28): http://downloads.activestate.com/Komodo/nightly/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment