Hello everybody,
same issue, same solution. With builds 4166 and 4169 it does not load some plugins. It won’t enable sort functions for example on Edit > Sort Lines, Permute Lines and won’t even start the Package Control: Install Package function.
@bschaaf
My python version is 3.10.11, could this be related?
Your system’s python installation isn’t used by Sublime Text. We ship our own python 3.3 and python 3.8 for plugins.
I had this problem starting immediately after installing the previous stable update (build 4152) up until the most recent stable update (build 4166), after which it disappeared as suddenly as it showed up.
In my case the problem was triggered by the SublimeLinter-flake8 plugin, but I’ve seen people reporting this error for dozens of different plugins. I believe this to have been an entirely ST-based problem.
Unfortunately the console was unhelpful, it just says “error: plugin_host-3.3 has exited unexpectedly, some plugin functionality won’t be available until Sublime Text has been restarted” after other completely normal logs.
In my opinion if the plugin host crashes there should be a full on stack trace displayed, exactly like what happens when an error is thrown in Python. I spent hours trying to figure this out with no luck and no solution except to wait for the next build and hope things would be better (luckily they were).
I hope the ST devs consider adding more debug information to this error, should it ever show up again. Just saying there’s an error doesn’t go very far for figuring out why.
This is openssl related.
On the Mac, where I use both openssl v1 and v3 via homebrew, I have unlinked v3 so that it finds openssl@1 and it works with ST 4 Buld 4116
I have not managed to figure out how to sort that, but since I was only testing ST there I didn’t bother.
The OpenSSL issue is an issue with package control and only applies to macOS with homebrew installed. It also afaik doesn’t cause the plugin host to crash, it just results in package control not working.
darn didn’t work for me.
$ brew unlink openssl@3
==> Downloading https://formulae.brew.sh/api/formula.jws.json
Warning: ignoring --capath, not supported by libcurl
################################################################################################################################################################################################################################################################ 100.0%
==> Downloading https://formulae.brew.sh/api/cask.jws.json
Warning: ignoring --capath, not supported by libcurl
################################################################################################################################################################################################################################################################ 100.0%
Error: No such keg: /usr/local/Cellar/openssl@3
$
When looking at the path, I only see the following folders:
/usr/local/Cellar/openssl
/usr/local/Cellar/openssl@1.1
$ brew search openssl
==> Formulae
glib-openssl openssl@1.1 ✔ openssl@3 ✔ openssl@3.0 openslp openssh opensaml opensc openmsx openfst opencsg open-sp
==> Casks
openmsx opensc opensim
==> Downloading https://formulae.brew.sh/api/cask_tap_migrations.jws.json
Warning: ignoring --capath, not supported by libcurl
################################################################################################################################################################################################################################################################ 100.0%
==> Downloading https://formulae.brew.sh/api/formula_tap_migrations.jws.json
Warning: ignoring --capath, not supported by libcurl
################################################################################################################################################################################################################################################################ 100.0%
haha yeah. I’m in way over my head with this one. Just hoping it was an easy answer I could learn from in reverse rather than searching through varios man pages, banging my head against the desk, etc.
Thank you!!! 
EDIT: Tried the latest suggestion.
Error: No such keg: /usr/local/Cellar/openssl@3
You used the backslash before the at sign?
I think you might find that brew info openssl will point to openssl@3 3.2.0 or similar, and if you do a brew unlink openssl you will find that the 3.2.0 version will be unlinked (but not removed).
Yes, copied and pasted directly from your previous post: brew unlink openssl\@3
1brew info openssl` returns:
$ brew info openssl
==> openssl@3: stable 3.2.0
Cryptography and SSL/TLS Toolkit
https://openssl.org/
/usr/local/Cellar/openssl/1.0.2q (1,794 files, 12.1MB)
Poured from bottle on 2019-03-10 at 00:17:28
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/o/openssl@3.rb
License: Apache-2.0
==> Dependencies
Required: ca-certificates ✘
==> Caveats
A CA file has been bootstrapped using certificates from the system
keychain. To add additional certificates, place .pem files in
/usr/local/etc/openssl@3/certs
and run
/usr/local/opt/openssl@3/bin/c_rehash
==> Analytics
install: 454,271 (30 days), 1,331,214 (90 days), 3,129,915 (365 days)
install-on-request: 65,579 (30 days), 186,657 (90 days), 512,899 (365 days)
build-error: 4,995 (30 days)
I then tried brew unlink openssl
$ brew unlink openssl
Unlinking /usr/local/Cellar/openssl@1.1/1.1.1q... 0 symlinks removed.
I then did brew info openssl again, and got the reame return as the previous time. 
Seems weird that there’s no folder for openssl@3 in /usr/local/Cellar/ - only the two I listed before: openssl and openssl@1.1
that’s the default…
Does the Package Manager work now? Don’t forget to restart :-)-O
Unfortunately, I rebooted my system after this, and I’m still seeing the same error when launching Sublime Text, and package manager is still not working.
Just in case this may make a difference, here are my specs:
Hardware Configuration:
Model Name: MacBook Pro
Model Identifier: MacBookPro14,3
Processor Name: Intel Core i7
Processor Speed: 2.9 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: 185.0.0
SMC Version (system): 2.45f0
System Software Overview:
System Version: macOS 10.12.6 (16G29)
Kernel Version: Darwin 16.7.0
Boot Volume: OSX
Boot Mode: Normal
Secure Virtual Memory: Enabled
System Integrity Protection: Enabled
Terminal app: Version 2.7.3 (388.1.1)
I happen to use the same macos version (Sierra) and I also had this problem. What worked for me was replacing my package control with beta9 (Package Control 4.0.0-beta9) and disabling automatic updates for it by editing Package Control.sublime-settings (“auto_upgrade_ignore”: [“Package Control”]). For whatever reason package control versions > beta9 don’t work for me.
Even not 4.0.0-beta10?
Final release 4.0.0 ships with latest asn1crypto and oscrypto libraries from https://github.com/wbond/oscrypto as they seem to ship relevant changes for latest MacOS builts and arm64 architectures. Those are therefore the most likely ones to blame, if beta10 still works.
If someone can verify beta10 to work, we could revert oscrypto to 1.3.0 release to see if it helps. Otherwise I can only drop that downloader completely as there seems rather low progress with that libraries, recently.
I just checked again to make sure. Yes, beta10 crashes on me, beta9 is the last one that works. Here are my debug logs for beta9 and beta10.
There are some changes between beta9 and 10 but nothing obvious, which could cause plugin_host to crash. As everything is running fine on my Windows boxes a MacOS user suffering from it, would need to do a bisect between those two tags to find the commit, which introduces the problem.
Otherwise running ST via a debugger could probably reveal a traceback to help sublimehq to narrow the reason down.
Without someone pointing to the reason I doubt I can do something to resolve this issue.