The new Notes client seems to run generally not very stable.
in my company there is a client wich crashes almost hourly, here the excerpts from the log.
does anybody know the reason???
Windows Dir : C:\WINDOWS
Arguments : “C:\Lotus\Notes\nsd.exe” -dumpandkill -termstatus 1 -dlgopts showwait -crashpid 2092 -crashtid 2356 -runtime 300 -ini “C:\lotus\notes\notes.ini” -svcreq 128
NSD Version : 8.5.10.9243 (Release 8.5.1)
OS Version : Windows/XP 5.1 [32-bit] (Build 2600), PlatID=2, Service Pack 3 (2 Processors)
Build time : Tue Sep 29 02:01:48 2009
Latest file mod : Tue Sep 01 22:08:33 2009
Notes Core Version : Release 8.5.1 (32-bit client)
Notes Standard Version : 8.5.1_20090929.1223
############################################################
thread 1/32: [ NLNOTES: 082c: 0934]
FP=0x00135c18, PC=0x7c91e514, SP=0x00135bb4
stkbase=0x00140000, total stksize=237568, used stksize=42060
############################################################
[ 1] 0x7c91e514 ntdll.KiFastSystemCallRet+0 (898,493e0,0,1363c8)
[ 2] 0x7c802542 kernel32.WaitForSingleObject+18 (898,493e0,136b5c,1367ff)
@[ 3] 0x601b4ec5 nnotes.FRSendCommandToService+789 (1363e8,1367e8,1367ff,0)
@[ 4] 0x601b5aff nnotes.OSRunExternalScript@8+1055 (12c,1)
@[ 5] 0x601b607f nnotes.FRTerminateWindowsResources+975 (1,1000,1,0)
@[ 6] 0x601b64a8 nnotes.OSFaultCleanupExt@24+984 (cb6a68,1000,0,0,0,136e84)
@[ 7] 0x601b652a nnotes.OSFaultCleanup@12+26 (0,1000,0)
@[ 8] 0x601c1a24 nnotes.OSNTUnhandledExceptionFilter@4+276 (1379c4)
[ 9] 0x089c7aa2 ltspln50.NlpEntry+113746 (1379c4,0,0,0)
[10] 0x7c34c456 MSVCR71._XcptFilter+351 (0,1379c4,7c34246e,1379cc)
@[11] 0x004026a3 NLNOTES.WinMainCRTStartup+471 (11ceac,7c91e920,7ffdf000,8054b6ed)
[12] 0x7c817077 kernel32.RegisterWaitForInputIdle+73 (4024cc,0,78746341,20)
WARNING (0):
Instruction Pointer is invalid, will attempt to extract first address from stack context
############################################################
FATAL THREAD 1/32 [ NLNOTES: 082c: 0934]
FP=0x00137dd8, PC=0x00360035, SP=0x00137da0
stkbase=00140000, total stksize=237568, used stksize=33376
EAX=0x0001ffff, EBX=0x0143e818, ECX=0x07ec245c, EDX=0x00000000
ESI=0x07ec2418, EDI=0x07ec245c, CS=0x0000001b, SS=0x00000023
DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00210216
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x6309f46f nnotesws.CNEMToolbarMgr::OnSelMgrChange+143 (2,0,0,2)
@[ 2] 0x6317d65e nnotesws.NEMToolbarUpdateUI@4+190 (58bc018)
@[ 3] 0x6317d720 nnotesws.SmartSTStatusChange@4+64 (1)
@[ 4] 0x6355a2e0 nnotesws.DeskIMLogin@4+1472 (2)
@[ 5] 0x6355aa63 nnotesws.AttemptIMLogonCallback@12+19 (1,0,139140)
@[ 6] 0x6355b4da nnotesws.DeskExecInMainThread@12+26 (6355aa50,139140,0)
@[ 7] 0x63556739 nnotesws.ReLoginToSametime+41 (2,3d55550,7ef7018)
@[ 8] 0x62664e9d nstclientu.STCGetUserStateList@16+669 (3d55550,133ffdc,ebe4598,5)
@[ 9] 0x63565fac nnotesws.DeskIMGetUserStateList@16+76 (3d55550,133ffdc,ebe4598,5)
@[10] 0x6397abc0 nnotesws.@DocRefreshSTStatus@16+432 (0,0,2502be,7ef7018)
@[11] 0x6304f6f3 nnotesws.@DocWindowsMessage@24+19187 (0,0,13967c,139670,0,0)
@[12] 0x63049bee nnotesws.DocRichTextWndProc@16+238 (7ef7018,849,0,0)
[13] 0x7e368734 USER32.GetDC+109 (63049b00,2502be,849,0)
[14] 0x7e368816 USER32.GetDC+335 (0,63049b00,2502be,849)
[15] 0x7e3689cd USER32.GetWindowLongW+295 (139790,0,1397b4,630b8feb)
[16] 0x7e368a10 USER32.DispatchMessageW+15 (139790,1,c0168,63020000)
@[17] 0x630b8feb nnotesws.NEMMainLoop@4+811 (4013a0)
@[18] 0x00401a2b NLNOTES.WinMain@16+1675 (630f7730,0,162306,1)
@[19] 0x00402651 NLNOTES.WinMainCRTStartup+389 (11ceac,7c91e920,7ffdf000,8054b6ed)
[20] 0x7c817077 kernel32.RegisterWaitForInputIdle+73 (4024cc,0,78746341,20)
############################################################
PASS 2 : FATAL THREAD with STACK FRAMES 1/32 [ NLNOTES: 082c: 0934]
FP=00137dd8, PC=00360035, SP=00137da0
stkbase=00140000, total stksize=237568, used stksize=33376
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
Disassembly of c. 10 instructions before and after faulting address 6309f46f:
6309f456 0fb7d7 movzx edx,di
6309f459 51 push ecx
6309f45a 52 push edx
6309f45b 8bce mov ecx,esi
6309f45d ff500c call dword ptr [eax+0xc] ds:015fa80d=a6809a95
6309f460 8b4df8 mov ecx,[ebp+0xf8] ss:017125e6=00000000
6309f463 8b93e2040000 mov edx,[ebx+0x4e2] ds:0143ecfa=06b13018
6309f469 8b01 mov eax,[ecx] ds:07ec245c=00020000
6309f46b 52 push edx
6309f46c ff507c call dword ptr [eax+0x7c] ds:015fa80d=a6809a95
FAULT ->6309f46f 8bd8 mov ebx,eax
6309f471 6685db test bx,bx
6309f474 7538 jnz 6309f4ae
6309f476 8b5df4 mov ebx,[ebp+0xf4] ss:017125e6=00000000
6309f479 83c701 add edi,0x1
6309f47c 663b7de8 cmp di,[ebp+0xe8] ss:017125e7=0000
6309f480 72cf jb 6309f551
6309f482 8b4df0 mov ecx,[ebp+0xf0] ss:017125e6=00000000
6309f485 83c101 add ecx,0x1
6309f488 663b4de4 cmp cx,[ebp+0xe4] ss:017125e7=0000
6309f48c 894df0 mov [ebp+0xf0],ecx ss:017125e6=00000000
6309f48f 7296 jb 6309f527