...and get no completion at all until I'm partway through typing the "atlasTexture" token at the end, and then the completion window that does finally come up at that point is actually showing completion for the "AssetDatabase" token from the beginning of the line.
When this occurs, if I open Activity Monitor and locate the mono process, it always looks something like this:
Restarting Sublime Text fixes the issue, but it will usually recur again within 10-15 minutes.
I've checked the debug console in Sublime Text when this state occurs but I don't see anything out of the ordinary. TBH I don't even know if it's really omnisharp-sublime's issue or if it's an issue with the server? But I don't really know how to track that down.
Rosalie241
commented
6 years ago
I'm on Mac OS X 10.10.3 using SublimeText build 3083 with the Package Control version of OmniSharp (1.9.3).
Frequently while working I'll notice the completion window becomes very slow to pop up. For example, I might type a line of code like this:
...and get no completion at all until I'm partway through typing the "atlasTexture" token at the end, and then the completion window that does finally come up at that point is actually showing completion for the "AssetDatabase" token from the beginning of the line.
When this occurs, if I open Activity Monitor and locate the mono process, it always looks something like this:
Restarting Sublime Text fixes the issue, but it will usually recur again within 10-15 minutes.
I've checked the debug console in Sublime Text when this state occurs but I don't see anything out of the ordinary. TBH I don't even know if it's really omnisharp-sublime's issue or if it's an issue with the server? But I don't really know how to track that down.