Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
GoSublime Crashing Sublime Text 3: MacOS X #911
I'm running into a very strange issue with the GoSublime plugin.
Currently, my setup is a MacBook Pro connected to 2 monitors. I have the laptop up on a stand with the clamshell open so from left to right my displays are MacBook Pro display -> 24" Asus 1080p (monitor 1) -> 24" Asus 1080p (monitor 2).
When I start new instances of Sublime (using
So, let's say I have an instance of Sublime open on monitor 1 and I want to open a new instance of Sublime for a different project than my first instance. I go to a terminal on monitor 2 and type
If my MacBook Pro display has a maximized application (in this case Slack) in focus, Sublime will go completely unresponsive. I have to force quit the application and start all over again.
However, if on my MacBook Pro Display I've changed to a workspace that's not a maximized application, I can spin up as many new instances of Sublime as I want and Sublime won't seize up.
The problem is, there's nothing in the logs to indicate any code errors. I do know, however, that if I disable the GoSublime package, this problem does not occur at all.
Sublime Text 3 is 3.1.1
Is there any additional information I can provide to help narrow down the cause of this strange behavior?
Thank you for the suggestions! Upgrading to the dev build changes the behavior of how new instances of Sublime start up. Instead of keeping the maximized application on-screen, it actually moves you to the workspace where the new window is created.
I'm not getting freezing issues anymore! Thank you very much for the assist! Issue resolved.
I'm having this issue as well with GoSublime 66dc145, Sublime Text 3189
Get's stuck after this command:
Works perfectly when I revert to 9be2a67
@DisposaBoy- I did initially try killing the margo processes but Sublime was still stuck- however, changing
After margo successfully loaded, I changed it back to