I reviewed the trace you attached previously and found that the UI delays were caused by an extension (Ref12).
#Visual studio 2015 intellisense slow update
Marek Sliwa on 12/11/2017, 08:19 PM (9 days ago): edit an enum, change the value by erasing the part after a dot, then the dot, then type a new fun little dot, and you'd expect intellisense suggest box, instead VS freeses and cpu goes to 100% on one of the cores, occured many times today, before and after 15.1 updatei suggest the visual studio team load a realistic solution and try to use visual studio for a while, clearly this isn't done in past months with these very low quality update releases. Upload your by choosing insert file tag on add comment field then submit after signing in. Trace will have up to several minutes of information only so it is important to stop recording as soon as the issue is reproduced.ĥ. It will take a while to process the trace, but at the end there should be a zipped file at c:\temp\.Ĥ. Once the issue is reproduced, you can click "Stop Collection" on the PerfView UI. After 3-5 seconds, you can start Visual Studio to reproduce the issue.ģ. This will launch PerfView UI and start recording automatically. Perfview.exe collect c:\temp\ReproTrace.etl -CircularMB:2048 -Merge:true -Zip:true -Providers:641d7f6c-481c-42e8-ab7e-d18dc5e5cb9e,*Microsoft-VisualStudio-Common -ThreadTime -NoV2Rundown From an admin command prompt, run the following to start recording: Download PerfView from and copy to a temp directory.Ģ. You are able to get the files with the following steps:ġ. Thank you for your feedback! In order for us to investigate this further, could you please give us an ETL trace file so that we can conduct further research?
0 kommentar(er)
