IDE lockups

I love the functionality of RS and have pretty much become dependent on it, but still I'm on the verge of giving up and cancelling my subscription due to its performance with large solutions. This is clearly nothing new or specific to my setup, I've lost count of the number of times I've heard people say RS++ has terrible performance.

What I really want to know is, why is it necessary for your extension to lock up the IDE? I mean ever, at all, let alone with the frequency it does. If it's going to take ages to reparse the source, or do whatever else it seems to want to hog my cpu for even when it's supposedly up to date, okay, I can live with it. But it's 2018, why does any of this need to block the UI thread? Can't you prioritize fixing this longstanding, crippling issue instead of adding more new functionality?

1 comment
Comment actions Permalink


Have you sent us any performance traces to investigate? If not, please try to capture UI lags on a timeline trace ( and we'll take a look at what causes them.

If the lockups occur randomly on a large solution, they are most likely because of garbage collection pauses which stop all the threads. In this case the standard advice is to exclude some parts of solution from indexing if you do not need them via the Third-Party code property page (, which should help with the total memory footprint.



Please sign in to leave a comment.