Extremely slow startup (on my PC)

[enzodan]

Hi everyone. I have a problem with vvvv gamma startup on my PC, it takes almost 10 min. Once it’s start everything is fine but it’s very annoying. Obviously the problem is on my PC, it doesn’t happen on other PCs. And just for information it doesn’t happen for vvvv beta on the same PC. I tried uninstalling gamma and using programs like CCleaner to eliminate any residue but the result is the same. The programming window appears, then there is a long wait before the window unlocks and the help browser screen also appears. I think there are libraries or other applications that slow down the startup process but I’m not an expert.Is there a way to understand what happens during program startup? Some sort of file log where to look for the problem? Thanks in advance!

[bjoern]

@sunep was reporting something similar in the chat not that long ago. Afair everything he tried to “fix it” failed and in the end he had to re-install Windows.

[enzodan]

Thanks @bjoern. I am seriously considering this solution even if it is drastic. I will do it as soon as possible. Perhaps it is not related to the problem but I remember that it started the day I was trying nugets like rcp, websocket or webserver. By the way once gamma started everything works correctly. vvvv4ever!

[bjoern]

@enzodan

Perhaps it is not related to the problem but I remember that it started the day I was trying nugets like rcp, websocket or webserver.

You could try deleting the nuget packages.

Stable:
C:\Users\YourUserName\AppData\Local\vvvv\gamma\nugets

Previews:
C:\Users\YourUserName\AppData\Local\vvvv\gamma-preview\nugets

[enzodan]

I already did it but unfortunately it doesn’t solve the problem. thanks anyway

[Elias]

@enzodan In the latest preview builds we added a new command line option --log which will enable logging to %UserProfile%\Documents\vvvv\gamma-preview\vvvv.log. There’s certainly room for improvement about what is being logged, but maybe (if you still have access to that machine) you could give it a spin and post the resulting log file here? We could then add more log statements to try to pin point the issue.

You’ll need to start vvvv with
vvvv.exe --log