none
Visual Studio 2015 Enterprise High Memory & CPU

    Question

  • I am using Visual studio 2015 Enterprise on initial load of a certain solution I have it is using 600MBS. There are about 20 projects in the solution although I do have others with more that use less. This number slowly goes up and has reached 1.6 GBS with contant CPU activity. Navigating the classes becomes slow and scrolling is nearly impossible as the lag is 3-4 seconds. Has anyone else experienced and found anyway of resolving it?

    My development system is a 12 core Xeon with 32GB of RAM so the machine isn't struggling an it only seems to be this one solution that has the issue at the moment.

    Stephen

    Monday, September 19, 2016 11:08 AM

Answers

  • It appears that the lagging/hanging issue in Visual studio was caused by CodeLens. The memory usage is still high but with 32GB that doesn't worry me a great deal. It's a shame did like a few features it provided but the degradation in performance is shocking!

    Just to note i have all the VS updates and the solution projects are all .net.

    Sj

    • Marked as answer by Sjb83 Wednesday, September 28, 2016 9:02 AM
    Tuesday, September 20, 2016 4:22 PM

All replies

  • Hi Stephen,

    It seems like a performance issue of the Visual Studio. It doesn't have an obvious solution.

    So first, we need to improve the performance of your PC. I suggest you to restart your machine and disable the anti-virus software and close other third party programs in your task manager.

    After that try to open your solution again. If still no help. I suggest you could workaround by this:

    You could split your solution. You could load only one or two projects  in your Visual Studio which you need to use. Don't load the whole solution.

    Best Regards,

    Lake Xiao

    Tuesday, September 20, 2016 2:41 AM
    Moderator
  • I am using Visual studio 2015 Enterprise on initial load of a certain solution I have it is using 600MBS. There are about 20 projects in the solution although I do have others with more that use less. This number slowly goes up and has reached 1.6 GBS with contant CPU activity. Navigating the classes becomes slow and scrolling is nearly impossible as the lag is 3-4 seconds. Has anyone else experienced and found anyway of resolving it?

    My development system is a 12 core Xeon with 32GB of RAM so the machine isn't struggling an it only seems to be this one solution that has the issue at the moment.

    Stephen

    Update: Please see bottom link first since it is update and I found it last.

    I found this link 5 Performance Tweaks for Visual Studio 2015 and large solutions after reading this thread VS 2015 memory usage and perf after some hours of use however I did not read all of the thread which I recommend you do since more is discussed in it which possibly may assist you.

    I've also seen where it is mentioned for anti-virus type software to set them to allow or disregard Visual Studio dev .exe and project folder path so project files are not constantly monitored I suppose. And clearing temp folder as necessary.

    I don't know what DevExpress CodeRush is but if you use it I also found this link Visual Studio 2015 Enterprise hangs when opening up a solution after installing CodeRush 15.1.5.

    Also see Microsoft Visual Studio 2015 Update 3 (KB3165756) - Bugs that are fixed in version 14.0. 25431.01, released on 09/14/2016 which maybe you already know about or have already installed and it is 5 days old since its release. See below bug fixes for this update which can be manually downloaded from link.

    Bugs that are fixed in version 14.0. 25431.01, released on 09/14/2016

    Issue 1

    Visual C++ IntelliSense requests may fail in sections of code in which multiple namespaces that are opened by a single macro expansion are active.

    To work around this issue, explicitly replace the macro with its expansion.

    Issue 2

    When you build multiple solutions in different instances of Visual Studio, false errors are sometimes reported in one of the instances.

    Issue 3

    Visual Studio may crash if you stop debugging and then resume debugging soon after.

    Issue 4

    Visual Studio may crash when you debug managed applications if IntelliTrace does not load.

    Issue 5

    When you upgrade the existing Extension SDK to a later version, the installation fails and you receive the following error message:

    The method or operation is not implemented.

    Issue 6

    Provides improved XAML designer reliability.

    Issue 7

    Text Editor settings now persist as expected. In earlier updates to Visual Studio 2015, text editor settings frequently reverted automatically.

    Issue 8

    The data binding dialog box is now displayed correctly when you use third-party languages.

    Issue 9

    When you deploy Windows Universal apps to certain Windows devices, such as Xbox One or HoloLens, you may receive one of the following error messages if you deploy the app to the device on which it was previously deployed:

    • DEP2100 : Cannot copy the file "c:\users\SomeUser\documents\visual studio 2015\Projects\App5\App5\bin\x86\Debug\ilc\resources.pri" to the target machine "127.0.0.1".

    • Unable to activate Windows Store app '134ebb6-879c-0483d-0bc130264_153eg2134dbg!App'. The activation request failed with error 'The package could not be installed because resources it modifies are currently in use'.

    Issue 10

    Reduces the memory footprint of Edit and Continue operations.

    Issue 11

    When you create a project that includes Application Insights by using Git, your CI build fails because the .gitignore file contains the ApplicationInsights.config file. To work around this issue, you can either run git add --force on ApplicationInsights.config, or you can remove the file from .gitignore. This update removes ApplicationInsights.config from .gitignore.

    Issue 12

    Visual Studio stamps the output of a PCL-targeting netstandard with a TargetFrameworkAttribute class that may generate MSBuild warnings when that PCL is referenced by other PCLs that target a profile. This warning is now removed by disabling the TargetFrameworkAttribute version check when another PCL references a PCL-targeting netstandard.

    Issue 13

    CodeLens uses excessive CPU when finding references for methods which implement common interfaces.

    Issue 14

    Fixed UI delay occurring occasionally after a build of certain Visual C++ projects.

    Issue 15

    In Visual Studio 2015 Update 3 with Windows 10 Tools 1.4.1, incremental deployment to same device will instead sometimes result in a full deployment.

    Issue 16

    This change addresses an issue in PCL targeting. The KB3165756 update (version 14.0.25425.01, released on August 2, 2016) introduced a change that addressed a problem that occurred when the Portable Class Library tooling targeted the .NET Framework 4.6, ASP.NET Core, or UWP 10.0. In this situation, the Portable Class Library tooling generated a project.json that used the "dotnet" TFM. The "dotnet" TFM is now obsolete and may no longer be supported by NuGet packages. The PCL tooling in the KB3165756 update was therefore changed to always target .NET Standard, even for specific target platforms. However, the fix in KB 3165756 was determined to be incomplete. Therefore, this update reverts the fix. Current versions of NuGet still check for obsolete TFMs and warn the user about them so that users can manually update the TFMs.

    Issue 17

    When you update some extensions in Visual Studio (including the Roslyn insiders extension), you may find that later instances of Visual Studio (after the immediate next instance) don't work. The fix was to update the Settings DLL that merges pkgdefs so that it matches what the devenv executable does. The workaround is to run devenv /updateConfiguration at a developer command prompt.

    Issue 18

    Fixes a bug that prevented Accelerated Massive Parallelism (AMP) from working in a multi-GPU environment when you use a Session 0 shell (such as in cluster nodes).

    Issue 19

    This fix makes sure that cleanup occurs between debug sessions and that you no longer have to wait between sessions.

    Issue 20

    Fixes a memory leak to increase designer stability.

    Issue 21

    Code that is generated for floating-point operations could be incorrect when it performs square-root calculations. This typically occurs in the following situations:

    • You compile by using the /fp:fast or /Qfast_transcendentals switch, and you use standard library functions to calculate the square-root.

    • You use the _mm_sqrt_sd/_mm_sqrt_ss intrinsic functions.

    This problem prevents the upper part of an XMM register from being cleared. This could allow later instructions that use that register to operate on invalid values.

    Issue 22

    Fixes an issue that prevented extended popup editors, such as the brush editor, from being displayed when you arrange items in the XAML designer's properties tool window by name.


    La vida loca

    Tuesday, September 20, 2016 2:54 AM
  • It appears that the lagging/hanging issue in Visual studio was caused by CodeLens. The memory usage is still high but with 32GB that doesn't worry me a great deal. It's a shame did like a few features it provided but the degradation in performance is shocking!

    Just to note i have all the VS updates and the solution projects are all .net.

    Sj

    • Marked as answer by Sjb83 Wednesday, September 28, 2016 9:02 AM
    Tuesday, September 20, 2016 4:22 PM
  • It appears that the lagging/hanging issue in Visual studio was caused by CodeLens. The memory usage is still high but with 32GB that doesn't worry me a great deal. It's a shame did like a few features it provided but the degradation in performance is shocking!

    Just to note i have all the VS updates and the solution projects are all .net.

    Sj

    Well in Visual Studio you can select "Send Feedback" to report a problem or send a suggestion. I suspect the inability to use Code Lens due to apparent Memory Leak would be a problem.

    I should think for the cost of Enterprise edition issues like that would be considered a major problem.

     

    La vida loca

    Tuesday, September 20, 2016 5:34 PM