This project has moved. For the latest updates, please go here.


Memory leak while editing large project


Similar to issue 2522. This is a new issue so that we can start from the beginning.

I skimmed through the comments for 2522. I'm sorry to see that you hadn't figured out what the problem was. I see that a very large solution was involved.

I've been seeing VS 2013 go into Not Responding... for several months, and when that happens, I usually close VS and restart it. If I don't restart it, at some point VS crashes.

However, lately this has been happening alot more, as my projects have grown.

What I see now is that if I change a file in the editor, devenv.exe starts running 100% CPU for several seconds and the memory size increases by about 50 MB. When it gets to around 3 GB, that's when it goes into Not Responding...

I don't mind sending you my code or any diagnostic info. Just let me know what you want. The attached zip file has the python files, and solutions and projects used. The solution is in the CodeToolsPy folder.

I've also installed a few Python packages. Most recently was the enum34 package, so perhaps this package is causing problems. I'll try removing the import statements for enum34 and see if this helps.

My solution has three projects and about 30 files, all python. Total about 100K lines, 4 M bytes.

VS About gives me the following...

Microsoft Visual Studio Premium 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
Version 4.5.51209

Installed Version: Premium

Team Explorer for Visual Studio 2013 06191-004-0456033-02905
Microsoft Team Explorer for Visual Studio 2013

Python Tools for Visual Studio 2.2.30718.00
Python Tools for Visual Studio provides IntelliSense, projects, templates, Interactive windows, and other support for Python developers.

Python Tools for Visual Studio - Django Integration 2.2.30718.00
Provides templates and integration for the Django web framework.

Python Tools for Visual Studio - Profiling Support 2.2.30718.00
Profiling support for Python projects.

Has there been any progress in resolving this issue already?

file attachments

Closed Dec 15, 2015 at 8:43 PM by crwilcox


mrolle wrote Oct 28, 2015 at 10:02 PM

Removing the two imports for the enum package didn't affect the behavior, even after closing and restarting VS.

Zooba wrote Oct 29, 2015 at 5:50 PM

Unfortunately it's basically stalled on rewriting the code analysis engine, which is a huge task that we haven't been able to do yet. All the recent memory leaks we've been seeing are "correct", in that the memory does need to stay around, typically until another file is reanalyzed.

Also, we're now handling all issues at and most of the team (including myself) are not monitoring CodePlex any longer.