Also see #53, https://community.devsense.com/d/53-unresponsive-extension
I'm running into a lot of short-term freezing issues lately. Often times when I save a change in code, or start typing, Visual Studio becomes unresponsive for a seemingly random amount of time. Sometimes seconds, sometimes almost a minute and sometimes (rarely) it never recovers, forcing me to either wait for uncertain periods of time, or force-close visual studio and go through the whole project load (which thankfully happens a lot quicker now) again. Sometimes every time I press backspace to erase a character in a twig file, I get exceptions that I have to confirm with ok. Twig files are often wrongly syntax highlighted and stay in that state until the file is closed and reopened. Sometimes intellisense doesn't pick up classes of composer libraries until I close and reopen Visual Studio. And sometimes intellisense decides not to work at all, not giving any suggestions until close the file and open it again.
As you may have noticed, I'm using the word "sometimes" a lot. Because it is sometimes, none of these issues are constant, but considering how many there are, at least some of them happen frequently, multiple times a day. Most annoying one is probably the random hang ups and freezes, forcing me to wait for seemingly random amounts of time, until Visual Studio recovers and tells me that this extension has caused unresponsiveness for X seconds.
In general I'm very happy with the extension and absolutely love the integration into visual studio. The debugger is top notch and full twig support isn't the most important thing in the world to me. However, with all these minor, yet unavoidable issues I'm recently growing slightly frustrated. Reliable operation under normal circumstances should always be top priority and I'd really like to see at least the unresponsiveness, freezes and exceptions resolved.
Sadly, Visual Studio log dumps are inconclusive and times of unresponsiveness seem to be the only times the Windows Event Log doesn't fire warnings or infos, so that's not a possibilty to track this all down either. The issues persist across multiple pc's (with slightly different results) and even fresh installations of windows. If there's anything to do to help you track those down, be it with a remote session (sadly, I can never tell when the issues will start arising and how often they do) or in other ways, I'm happy to do so. But please resolve this.