This project is read-only.

Typescript project running in VS 2012 is now unusable!

Topics: General
Feb 26, 2014 at 7:46 PM
After upgrading to the 1.0 RC, things are much worse.
Prior to this upgrade I've seen what seems to have been memory leaks in VS and frequent freezing of the browser (many times it freezes when I try to dynamically add a break-point during run-time, or by simply trying to step-into a typescript function).

Now, after the 1.0 RC, I noticed the following:
  • Noticeably massive sluggishness all around from VS 2012.
  • Double-clicking to highlight a word takes a noticeable delay.
  • F12 (to goto definition didn't work) - this appears to have been fixed after doing a Repair install again.
  • Unable to set breakpoints in Typescript ("This is not a valid location for a breakpoint").
  • Intellisense is not working.
Feb 26, 2014 at 8:14 PM
Could you expand on the characteristics of your project where you're seeing this? Or is this happening for all projects now?
Feb 26, 2014 at 8:18 PM
I only have one project, under one solution.
Can you confirm that I should not be seeing these issues under VS 2012?
Feb 26, 2014 at 8:28 PM
Just to add to this...

The issue that is THE MOST frustrating is the freezing.
The entire IDE freezes, and it takes several seconds (more than a mere 5-10 seconds sometimes) before VS decides to behave again.
Note that during this freeze-up, the Memory and CPU usage seems normal (they're not high in usage whatsoever).
Feb 26, 2014 at 10:20 PM
If intellisense is not working at all, you may be in a bad state with the install. We've seen this on rare occasion.

To work around it, you may want to try uninstalling, making sure your C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\TypeScript directory is clean, then installing again.

If that doesn't fix it, please let us know.
Feb 26, 2014 at 11:54 PM
@jonturner. Things are looking much, much better now... Thanks!
Feb 27, 2014 at 12:00 AM
FYI, everything is better, BUT, the performance (sluggish) issue is still painfully present.
Feb 27, 2014 at 12:16 AM
...And one more thing: Go-to-definition (F12), it seemed to be working after i did a fresh install.
But after a moment of coding it now seems to be broken again.

Feb 27, 2014 at 1:09 AM
I lost the ability to set breakpoints again.

Feb 27, 2014 at 1:41 AM
I moved over to VS 2013. So far it feels better.
If this resolves my issue(s), then can we safely say there is an issue with Typescript and VS2012 integration???
Feb 27, 2014 at 2:58 AM
You are certainly not the only person using TypeScript on VS2012 so if it was always this bad we would know ;) You may certainly have hit some bug causing performance issues but without a consistent repro performance issues like this will be very hard to track down.
Feb 27, 2014 at 3:02 AM
If it helps, the file size of my single, .js file which is generated by all of my Typescripts files put together (easily more than 20 files with many classes per file), is over 500 KB.

Feb 28, 2014 at 9:58 AM
I'm experiencing the same issues in VS2013.

Freezing between moving the caret is extremely frustrating. Removed all my extensions bar Visual SVN and still experiencing freezing issue. I have a 0.5-1 sec delay in moving the cursor.

I also cannot set breakpoints on code that I previously could.

For now I've rolled back to ver 0.9.5 which is all working correctly.

Not the end of the world as it is an RC, but was looking forward to getting my hands on 1.0.
Mar 1, 2014 at 1:10 PM
I'm also experiencing freezes on VS 2013. Two places I'm certain freezes happen every time are:
  1. When renaming a TS file, VS will freeze for 5 seconds
  2. Copy/Paste a file in the same project, VS will freeze when I paste the file
Other than that, I also experience random freezes when saving a files, sometimes takes 2-3 seconds without being able to move the cursor. This happens exclusively with TS files. I have more C# files than TS files in my project, and they don't cause these issues.

These freezes are not new to TS 1.0 RC, I remember having these since started using TS, but have seem less of them lately.

On 0.9.5, sometimes I had freezes I had to force close VS 2013. Looking at Procmon when that happened looked like an infinite loop of some kind, as I could see the same calls to TSC being made again and again with 100% cpu usage. Didn't get this kind of freeze with 1.0 RC yet, but I have been using it only for a couple of days.
Mar 2, 2014 at 9:42 PM
I'm not experiencing any freezing across a relatively large codebase in VS 2013.

However, performance in the 1.0RC is down across the board.

This includes both project compilation and intellisense in Visual Studio.

This is a shame because many other outstanding issues appear to have been resolved.
Mar 4, 2014 at 8:39 AM
I'm using VS 2013 Express for web and faced the same issues (F12, intellisense, etc... no more working) after an upgrade from 0.9.5.
In fact when I opened a file, the 2 list boxes on top of the edit window displayed "refreshing..." and never left this "state".

I uninstalled TypeScript, directly reinstalled 1.0 RC, same issues.
I applied the patch, but same issues.

Finally I reinstalled 0.9.5...
Mar 4, 2014 at 4:05 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Mar 4, 2014 at 4:06 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Mar 4, 2014 at 4:07 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Mar 4, 2014 at 4:44 PM
Sounds like there are a few different issues. I've created separate work items for the "refreshing..." forever, degraded performance, and IDE freezing. If you have any more information that might help us track down what's going on, please add it to the items.
Mar 4, 2014 at 6:17 PM
Since I'm not sure all of you are tracking the issues in the issue tracker, I'll add this here.

The TypeScript tools in VS only invoke the compiler when actually compiling the project. It sounds like there is an extension interfering with your experience, do you have any installed? Like Web Express, Resharper, etc.

The easier to find this is in Help, About, and than use the "Copy Info" button.

It would be helpful if you can add that information to the issues Jon created.
Mar 4, 2014 at 6:43 PM
Yes, I have WebEssentials/Typescript on my VS 2012.
Should this be uninstalled?

If so, it should be clear somewhere to uninstall things.

Mar 4, 2014 at 7:26 PM
Tools -> Extensions and Updates

You can disable or uninstall from there, you should also make sure those extensions are updated.
Mar 4, 2014 at 8:12 PM
paulb wrote:
The TypeScript tools in VS only invoke the compiler when actually compiling the project.
@paul, doesn't the TypeScript language service run constantly in the background when one is making edits to TypeScript files?
Mar 4, 2014 at 8:34 PM
@nabog yes the language service runs, but that runs as part of the devenv.exe process not the tsc.exe process.
Mar 5, 2014 at 8:23 AM
Before rolling back to 0.9.5 I disabled all extensions and then uninstalled them too, this made no difference in my case.
Mar 6, 2014 at 12:59 PM
Is there anything we can do to provide more info to solve these problems other than "try to uninstall all extensions"?

I'm using VS 2013 and today intellisense stopped working on TS files, no updates, no changes to the project. Was working fine yesterday, I'm pretty sure if I just reboot or wait a while, it will be back magically again as usual.

It seems strange to me that 3rd party extensions are affecting typescript so much for so many people, but have no effect on any other language on VS. Something is not right. Should TS be so fragile compared to other languages VS supports?

Also, there are people on my team complaining about this, but they don't use the forum, and are just expecting 1.0 final to have this sorted out. So, not everybody having these problems are reporting it.

Is there a way we can help trace this issue or even find out exactly what is causing it?
Maybe a way to run VS in some "debug mode", that generates a log we can send? Even a procmon trace, I don't know.
Mar 6, 2014 at 1:22 PM
Maybe look at
It was linked to using a specific output directory.
Mar 6, 2014 at 1:29 PM
This seems unrelated to the problem I'm experiencing.
Mar 13, 2014 at 6:32 PM

I've been doing some refactoring inside a fundamental part of the codebase today and TypeScript seems to be showing a pattern of causing VS to hang for periods of up to a couple of minutes.

The solution within Visual Studio 2013 Ultimate looks like this.

1. Project A
    - Interface A
    - Interface B
    + 100 or so interfaces.
2. Project B
    - Class A implements interface A
    - Class B implements interface B
    - Plus other classes that reference and implement other interfaces from Project A
3. Projects C, D, E etc have a total of 300+ classes that
     - reference Interface A and B from Project A.
     - reference  and implement other interfaces from Project A
Each project is compiled into an out file. All modules are internal and files import types via <reference>.

Today, I was porting some methods from Interface A to Interface B. After the cut and paste operation in Project A, I started refactoring code in Project B. At this point there was a consistent delay in the editor and the red squiggly line started becoming quite sticky. A couple of times I started seeing the circular toilet bowl of death and VS become unresponsive for a few minutes, before returning back to normal.

The problem as I see it is since 1.0RC when a change is made in a part of the codebase that is heavily referenced by other parts of the codebase the stickiness and hang ups start kicking in.

The overall compilation time is also down.

This is obviously not a lot to go by, but I hope it provides an insight or two into the problem.
Mar 24, 2014 at 1:15 PM
Another identifiable case that is causing sluggishness (as noted by @nvivo above) is when a file is renamed in Visual Studio.

The renaming itself is also slow: for control to return to the editor from the point of renaming can take a number of seconds (I counted 10 just now). Often it's the first renaming that is slow, and subsequent renaming can be faster.

Following a rename, where the class within the file is also renamed, there is a noticeable slowdown in the IDE, with "refreshing" showing up for extended periods.