| T O P I C R E V I E W |
| sergey.filippov |
Posted - Mar 06 2020 : 03:15:36 AM
Update of VA takes too long - about 25 minutes.
During the process, I can see that the devenv.exe process reads every file in the AppData\Local\Microsoft\VisualStudio\16.0_9d332929\Extensions\a0zzkl0w.fpe\Data
folder that was about 4 GB in size. After the update that folder was gone. New Data folder for the extension were about 50 MB in size.
That is great that the space was reclaimed but it seems the result would be the same as if I completely removed the previous folder. Why it is necessary to process old data folder?
P.S. During the process all files were kept opened. The devenv.exe process had about 100K opened handles. Looks like a bug. |
| 8 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - May 27 2020 : 09:19:27 AM
Thank you for the update. 3 minutes still seems a bit slow, unless your machine was busy doing something else, but it is clearly a massive improvement over 25 minutes.
I hope after the update everything is working well and running smoothly for you. |
| sergey.filippov |
Posted - May 27 2020 : 04:38:16 AM
Just for information.
I've just updated VA again. This time, I disabled F-Secure before updating.
I did not note exact time the process took, but it finished less than in 3 minutes. |
| sergey.filippov |
Posted - Mar 10 2020 : 06:12:10 AM
@accord
Thank you for forwarding the problem.
@feline
After the update everything is working correctly. I'm using F-Secure antivirus.
@sean
Thank you for the hint with alternate directory.
Okay, then deleting the extension directory before updating would solve my problem. That is enough to know for me for now.
Next time I'm going to update VA, I will experiment with antivirus and alternate directory. |
| sean |
Posted - Mar 06 2020 : 3:41:07 PM
Installing a different version of VA causes VS to create a new directory and delete the old directory -- that's just the way VS handles extensions.
By default, VA creates its symbol database in the extension directory so that if a user uninstalls VA, the data is automatically deleted (uninstalling a VS extension does not allow for any extension code to run -- VS handles disk cleanup).
You can tell VA to use a different directory for the symbol database:
https://docs.wholetomato.com/default.asp?W332
Then VS won't iterate over the VA symbol database files.
When you install an update of VA, it will purge and rebuild the database files. |
| feline |
Posted - Mar 06 2020 : 2:56:10 PM
The VSIXInstaller is a Microsoft installer that processes the VSIX file that extensions are packaged in. These are nothing more than renamed zip files.
I have never noticed the VSIXInstaller launching the IDE, but to be fair I have never seen a VA update take so long to install on any of my machines.
Does everything seem to be working correctly and normally now?
What anti-virus do you use? I am just wondering about a possible interaction between anti-virus and the update and the scanning of all the data files. |
| accord |
Posted - Mar 06 2020 : 2:46:39 PM
Yes, makes sense. Not sure if we can change how it works since the installation is done by Visual Studio itself, but I'll ask someone to take a look at this thread, who may know more about this. |
| sergey.filippov |
Posted - Mar 06 2020 : 10:20:44 AM
I used exe installer.
I did close all instances of Visual Studio.
I have Windows Event Logs with all process start/termination activity. It confirms that Visual Studio was closed before VA_X_Setup2366_0.exe was started.
According to it, VA_X_Setup2366_0.exe started VSIXInstaller.exe, that started devenv.exe. (Devenv.exe was started with the following command-line parameter: /updateConfiguration.) That devenv.exe was running for approx 25 minutes.
Apparently, that was the instance that wasted time by processing AppData folder. |
| accord |
Posted - Mar 06 2020 : 08:24:21 AM
Did you try to update using
- extension manager from inside Visual Studio
- or the downloaded .vcix installer, from Visual Studio gallery
- or the exe installer from our website?
When you install through the exe installer, you should exit all instances of Visual Studio, so there shouldn't be any devenv.exe process running. |
