FileViewer.com

Hi V folks,

Periodically, V (version 12 SR1) will crash, while viewing a text file that is located on a Windows server, with the file in active use by a process running on the server.
Is this unavoidable? If not is there a V option I should select to avoid this crash?
The Crash-????.dat file that is typically produced contains this information:

Exception 0xc0150010
in module C:\Windows\SYSTEM32\ntdll.dll at 001b:776e3e3c.

Exception handler called in Unhandled Exception Filter.

Version Information:

OS : 6.1 (Build 7601)
x32: Service Pack 1

FileVersion: 6.1.7601.17514
ProdVersion: 6.1.7601.17514
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
ProdVersion: 6.1.7600.16385

42% memory in use.
2048 MBytes physical memory.
2048 MBytes physical memory free.
0 MBytes paging file.
0 MBytes paging file free.
2048 MBytes user address space.
1924 MBytes user address space free.

32 Bit Context:
EDI: 0x0037d128 ESI: 0x00000000 EAX: 0x0412fd94
EBX: 0x002f8630 ECX: 0x0412fe38 EDX: 0x00000000
EIP: 0x776e3e3c EBP: 0x0412fdf0 SegCs: 0x0000001b
EFlags: 0x00000202 ESP: 0x0412fd8c SegSs: 0x00000023

Bytes at CS:EIP:
e9 b1 f2 fc ff 83 c1 08 89 75 ac c7 45 b4 03 00 00 00 89 75 b8 89 4d bc 8b 07 c7 45 a4 10 00 15
Stack begins at 0x0412fd8c
Return Address: 0x7768f754 (0x0412fdf4)
Parameters at : 0x0412fdf8

0x0412fd8c: 00000000 002f8330 c0150010 00000001 00000000 776e3e3c 00000003 00000000 ....0./.............<>nw........
0x0412fdac: 0412fe38 00000000 002f8630 0412fdd8 0412fe30 0112fe30 0412fde4 776b89d8 8.......0./.....0...0.........kw
0x0412fdcc: 76be0000 00000003 00000000 002f8630 00000000 002f8330 0412fe30 7768f73a ...v........0./.....0./.0...:.hw
0x0412fdec: 76bf49e5 0412fe88 7768f754 7768f742 5946e64b 003812c8 00000000 00000304 .I.v....T.hwB.hwK.FY..8.........
0x0412fe0c: 00260000 00000000 01a622c8 0412fe58 005caa3c 00260000 00000000 005caa5b ..&......"..X...<.\...&.....[.\.
0x0412fe2c: f578ba37 00000024 00000001 00000000 0000010b 00000000 ffffffff ffffffff 7.x.$...........................
0x0412fe4c: 7768f719 00000000 002f8330 003809a8 002f8630 76bf49e5 7ffd5000 7ffd3000 ..hw....0./...8.0./..I.v.P...0..
0x0412fe6c: 01a58f60 0412fdfc 0412f988 0412ff38 7767e0ed 2a3f134b 00000000 0412fe98 `...........8.....gwK.?*........
0x0412fe8c: 7768f63b 01a58f60 00000000 0412fea4 005cf0a3 00000000 0412feb8 00598259 ;.hw`.............\.........Y.Y.
0x0412feac: 00000000 0012ea70 00000000 0412ff44 00598771 00000000 00000001 f578bb2b ....p.......D...q.Y.........+.x.
0x0412fecc: 00000000 01a622c8 01a622c8 00000000 005eba64 00000001 00000000 00000000 ....."..."......d.^.............
0x0412feec: 00000000 00000001 00000000 0032b780 00000000 2a3f1200 00000000 00000000 ..............2.......?*........
0x0412ff0c: 005eb9d4 005eba48 00000000 00000000 00000000 00000000 00000000 00000000 ..^.H.^.........................
0x0412ff2c: 00000000 01a58f60 0412fec8 0412ff6c 005e10d6 00000000 0412ff7c 005cf0bf ....`.......l.....^.....|.....\.
0x0412ff4c: 0012ea70 f578bb13 00000000 01a622c8 01a622c8 c0150010 0412ff50 0412f984 p.....x......"..."......P.......
0x0412ff6c: 0412ffc4 005cf280 f10e019f 00000000 0412ff88 005cf167 00000000 0412ff94 ......\.............g.\.........
0x0412ff8c: 774fed6c 01a622c8 0412ffd4 776c37f5 01a622c8 5946e717 00000000 00000000 l.Ow.".......7lw."....FY........
0x0412ffac: 01a622c8 c0150010 77510651 77510651 0412ffa0 0412f988 ffffffff 7767e0ed ."......Q.QwQ.Qw..............gw
0x0412ffcc: 2a3f0abb 00000000 0412ffec 776c37c8 005cf0e5 01a622c8 00000000 00000000 ..?*.........7lw..\.."..........
0x0412ffec: 00000000 00000000 005cf0e5 01a622c8 00000000 Exception encountered during stack dump.
Stack Trace:

776e3e3c
7768f754
7768f63b
005cf0a3
00598259
00598771
005cf0bf
005cf167
774fed6c
776c37f5
776c37c8

End Trace

[EOF]

Periodically, V (version 12 SR1) will crash, while viewing a text file that is located on a Windows server

Thanks for the crash report. Unfortunately, it only tells me that the crash occurred inside Windows code (NTDLL.DLL)!

with the file in active use by a process running on the server

Is the file being *written to* by the server process?
Do you have *tailing* enabled in V?

Do you recall exactly when the crash happens? Does it happen as you are viewing the file? Or does it happen when you switch away from V and then switch back to it?

Can you please select "Send Error Report" from the Help menu and send me all the files that are listed (including any V.LOG files).

Thanks,
Charles.

Yes, the file is being written to by a process on the server.
No, tailing is off.
The crash takes place after I exit viewing the file. I believe the crash takes place s after I fully exit V, but am not 100% certain. If/when it happens again I will make sure to note the definitive circumstance.
Unfortunately I deleted all of the V.log files. I will save and send them to you if/when they are generated.

Thanks for the rapid reply. In all of my years of using V this is the first time I've ever experienced a crash.

Dave

I located the V.log that should have details on the crash. I just emailed it to you.