-
Notifications
You must be signed in to change notification settings - Fork 81
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
"plugin_host has exited unexpectedly" message #17
Comments
It could happen if the underlying program produces a segfault. What program were you running? |
OHHH. Yes, that makes total sense. I've been testing a Stan model on a bunch of simulated datasets in R, and it was indeed producing segfaults. I didn't make the connection since the error messages aren't printing in Terminus (unlike, say iTerm). But that's almost certainly the cause. I suppose it would be nice if segfaults didn't have such a dire effect on Terminus and Sublime Text, but this seems like a pretty minor issue now that I know what's going on. I'll close the issue. Thanks! |
Running the program via a shell instead of running it directly should capture the segfault (untested though). |
Ahh okay. Maybe I'll try to reproduce it and see what happens. |
I was wrong, running the program via a shell doesn't catch the segfault. |
turns out that it is a Sublime Text bug: sublimehq/sublime_text#2327 downgraded to Sublime Text 3161 and the issue is gone |
Let's keep it open until upstream fixes it. |
Sounds good! |
How can i get the sublime problem solved? |
The only solution now is to downgrade to 3161. Per the dev from sublime hq, a new build with the fix will be released soon. |
How do i downgrade to 3161 Randy? |
From the official website. However, you might need a license, otherwise it will keep asking you to update Sublime Text. |
From Sublime Text dev
|
fixed with dev version 3179. |
After using Terminus for any significant period of time (say, more than 30 minutes), I eventually get a pop-up message saying "plugin_host has exited unexpectedly, plugin functionality won't be available until Sublime Text has been restarted."
Not sure what info would be helpful here, but to start, I'm running ST3 (build 3176) on MacOS 10.13.5. Happy to provide whatever additional details would be of use.
The text was updated successfully, but these errors were encountered: