-
-
Notifications
You must be signed in to change notification settings - Fork 816
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
GutterColor slows down opening Install command panel #1646
Comments
I don't see any relations or reasons for such delays, nor can I reproduce them with GuterColor installed on Windows 11. Package Control already uses dedicated threads to run background tasks, instead of relying on ST's worker thread, to not be delayed by or delay other plugins. And it runs on another plugin_host. |
I don't see the connect either, yet it's there, the safe mode test with a single packages proves it |
Tried with its test.css open - no delay. |
If a plugin gets slowed down by another one running on a separate plugin_host, the only possible reason may be related with inter-process-communication or with API thread safety mechanisms. Package Control downloads and parses information in a dedicated background thread with little to no application of sublime API calls until the final step of creating the quick panel with the list of pre-built items. There's nothing to do to run it more independently. |
While troubleshooting #1645 I've discovered another puzzling issue: installing and using (having it active in an opened file) https://github.com/ggordan/GutterColor increases the time to open the
Package Control: Install package
command panel:I realize it's an old plugin, but still believe it should not have these kidns of side effects on this core ST package
nothing is going on in the log, same with and without the plugin (there is a bunch of network calls on the first Install command, )
(also checked within the safe mode with just two packages isntalled: package control and guttercolor and a custom theme, ignoring GutterColor restores performance)
The text was updated successfully, but these errors were encountered: