I just updated from V12 Preview 3 to Preview 4 on my Windows 7 x64 machine. A couple of times in the last day I've had V just sit there in a 'Not Responding' state using approximately 10% of my CPU cores.
I'd been viewing a file.. I'd closed the Find Files/GREP window, and then changed focus to do some work (in Visual Studio), and when I changed focus back to my V window (to load up a new file) that's when it became unresponsive.
Using 'Process Explorer' from the Sysinternals tools, shows that one of the threads (with a start address of 'v.exe + 0x2a8468') associated with V is responsible
Code: Select all
Unfortunately, I'm unable to provide a minidump. I did generate one, but while looking at the contents it appeared to have sensitive contents in it that I can't send out (as this crash is my development machine at work).
I had no stability issues with Preview 3.