TypeScript 0.9.1 Locking Up Visual Studio 2012

I'm having trouble using the 0.9.1 release in VS. I have a large solution with a handful of projects some of where depend on others. Upgrading form 0.9.0.1 there are some build errors (and they're all logical, no issues there) but while trying to fix them
Visual Studio is hanging. I find I can make about one significant change to the code okay; then another one and VS will hang for a while and eventually come back; on the next edit VS will gobble up CPU and eventually drop down to 0% usage but never come back.
It's like it's deadlocked.

Is anyone else having a similar issue? I tried fresh installs but that didn't fix anything.

There are a couple bugs that appear to be related to certain .d.ts files (namely linq.d.ts) and certain patterns with generics. These should be in the issue tracker, though please feel free to add a new issue if none match what you're seeing, so that we
can look into it.

I'm finding that when I have any typescript error in the errors list window that VS2012 will sometimes lockup ( 1 cpu pegged at 100% ) if I hover over the line, especially if the message is very large.

The change in compiler arguments is also pain ( dropped "-c") as we can't run both 9.0.1 and 9.1.0 in our dev team ( i'm testing the 0.9.1 drop but I can't compile without changing the arguments in the project file )

I've been quiet on this issue because we've been busy here but in my spare moments I've been setting up clean VM instances of Windows 7 and Windows 8 to test TypeScript 0.9.1 on. Win 7 doesn't seem to run nearly as efficiently as Win 8 on Hyper-V and there's
a million updates to apply.

Using the exact same code base I made trivial edits suggested by tslint on Win 7 and then on Win 8. The Win 7 instance had no issues besides Intellisense being slow (which I think is expected). The Win 8 instance would slow down VS and finally crash within
about 5 minutes consistently. I think this is conclusive proof that there's a problem with the TypeScript plugin, and it's not a conflict with other extensions.

I would guess that the issue is triggered by the size of the code base, but obviously I don't have permission to hand you my own. It wouldn't be too hard to machine generate a code base of hundreds of classes to stress test the plugin/compiler.