PTVS stays in the memory after exiting Visual Studio 2013

May 25 at 1:56 PM
Could you please solve this problem?
Coordinator
May 25 at 6:49 PM
Are you concerned about the background analyzer continuing to run? This is the only thing that shouldn't be freed when VS exits, and it's important that it gets to finish or else we'll have to start it all over again next time you start (it only runs once per environment, and then does incremental updates).

If you're referring to something else, we'll need some more information about your concern.
May 26 at 9:29 AM
yeah , but it seems that the program occpied too much resources of CPU,can you just optimize it ?
Coordinator
May 26 at 3:40 PM
CPU or memory? Ultimately, it has to use quite a bit of both because it's working on a CPU and memory intensive task. There aren't any more significant optimisations that we can make without compromising the results (code completions for the standard library and other installed libraries). If it's running out of memory and crashing then there may be something unexpected about your configuration or a library you have installed.

It should be running at low priority, so it shouldn't affect other processes. Inside VS you can see the progress (View, Other Windows, Python Environments), and there's no real harm in killing the process except that it has to start all over again next time you use PTVS.

If you look at the progress and it appears to be stuck, hovering over the progress bar should show which library is the problem. If this is the case, let us know and we will be able to help you some more.
Coordinator
May 26 at 9:24 PM
I wonder if, perhaps, we should provide some indication that it is running if it is left behind after closing VS. Say, something like a tray icon with a context menu that allows killing it, and a popup that appears as VS is closed saying something along the lines of "PTVS is still analyzing your standard library, click here to cancel".