I've got a 4th hang, also uploaded.
I was searching in a very large file.
As usual, CAS-F2/F9 had no effect.
I started another instance (with vs +new) to continue working and allow the first instance some time to think things through - maybe it was just going to wait for a long time?
Soon, the 2nd instance hung when I attempted to open a new file (with the WIndows file open dialog).
So, I attached a debugger to the first instance and wrote my dump file.
As soon as the first instance was terminated, the 2nd instance unlocked - almost as if the 2nd instance was waiting on something the first instance was holding.
From procmon this is was I saw:
172 14096 13628 2:09:29.4357577 PM vs.exe Process Exit SUCCESS Exit Status: 0, User Time: 146.4069385 seconds, Kernel Time: 36.3794332 seconds, Private Bytes: 229,457,920, Peak Private Bytes: 254,844,928, Working Set: 383,315,968, Peak Working Set: 406,142,976
173 14264 10840 2:09:29.4750133 PM vs.exe Thread Create SUCCESS Thread ID: 10124
Presumably the new thread (and the bunch of activity just after) has something to do with the WIndows file open dialog.
WRT #1 and #3: I *never* intentionally drag-n-drop text. I usually disable that feature, but I've not got around to it since installing the new slick edit.
I can believe all 3 are clipboard related.
#4 appears to have more to do with the Windows file open dialog.
I think that I had just copied a line of text (containing a file path), then attempted to open the file-open dialog. I intended to paste the filename there to open the file.
But, the dialog never appeared.