V12 Preview 4, Win7 x64, Lockup

[Dean Ashton]

Hi,

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

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x7d2
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x94
ntoskrnl.exe!KeStackAttachProcess+0x11c1
ntoskrnl.exe!ObReferenceObjectByPointerWithTag+0x233
ntoskrnl.exe!KeReleaseSpinLock+0x2a
mfeavfk.sys+0xdb11
mfeavfk.sys+0x7994
mfeavfk.sys+0x3105
mfehidk.sys+0x1791a
mfehidk.sys+0xc4d5
mfehidk.sys+0xced6
mfehidk.sys!DEVICEDISPATCH::DispatchPassThrough+0x98
ntoskrnl.exe!NtClose+0x3ef
ntoskrnl.exe!ObCreateObject+0x544
ntoskrnl.exe!SeAssignSecurityEx+0x751
ntoskrnl.exe!SeAssignSecurityEx+0x664
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
ntdll.dll!NtClose+0xa
KERNELBASE.dll!CloseHandle+0x13
kernel32.dll!CloseHandle+0x41
v.exe+0x19cb53
v.exe+0x19d00b
v.exe+0x1ba769
v.exe+0x1a54c7
v.exe+0x1fe79d
v.exe+0x1fa50c
v.exe+0x28658f
v.exe+0x269a16
v.exe+0x263308
v.exe+0x267596
v.exe+0x267651
USER32.dll!SetPropW+0xe1
USER32.dll!IsDialogMessageW+0x19b
USER32.dll!IsDialogMessageW+0x1e1
ntdll.dll!KiUserCallbackDispatcher+0x1f
USER32.dll!FillRect+0x76
USER32.dll!FillRect+0x88
v.exe+0x261956
v.exe+0x2614a7
v.exe+0x1975a3
v.exe+0x2bf307
v.exe+0x2a841a
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x21

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.

Regards,
Dean

[FileViewer]

A couple of times in the last day I've had V just sit there in a 'Not Responding' state

Is this something that you can reliably reproduce? If so, can you give me the exact steps to reproduce it?

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.

Was the file window still open when you switched back to V? If so, were you perhaps tailing the file?

Select Send Crash Report from the Help menu. If any files are listed, please send them to me.

Thanks,
Charles.

[Dean Ashton]

Hi,

It's not something I've been able to reproduce with any reliability, I''m afraid. And there are no logs available.

The file window was still open when I went back to V.

Incidentally, I've found another (thankfully reproducible) crash in Preview 4. If I open the Find Files/GREP dialog, select the 'Text Search (GREP)' page, and have 'Regular Expression File Mask' checked - but have the 'In files named:' text area empty, then V crashes.

Regards,
Dean

[FileViewer]

And there are no logs available.

Is there a V.log in C:\users\UserName\AppData\Roaming\V? If there is, please send it to me.

Incidentally, I've found another (thankfully reproducible) crash in Preview 4.

This will be fixed in the next release.

BTW: Are there any removable or network drives on your system?

Thanks,
Charles.

[Dean Ashton]

Is there a V.log in C:\users\UserName\AppData\Roaming\V? If there is, please send it to me.

No, I have a VSetup.log file present in that location, but no V.log file.

BTW: Are there any removable or network drives on your system?

Actually, yes. I have a number of network drives (which are persistent, having been set up during our domain logon scrips), I often use removable USB devices (although I don't tend to use V on contents of these USB devices) , and I also have a PGP Disk Volume that I mount and actually use V on fairly regularly. This latter drive dismounts after a certain amount of idle time. I'm at home right now, unable to get more information until Monday, but I wonder if there would be a problem if a drive dismounted while the Find Files/GREP window was open (or similar)..

I know it's a long shot, but if you have a PDB for the application I could try and get a more useful callstack from crashes I encounter (I appreciate that it may not be possible or desirable for you to make a PDB file available though - I'm just throwing it out there as a possible way forward).

Thanks,
Dean