Go to your calendar and perform a search (Ctrl-F). Enter in a text string that it will NOT find, and select a “backward” search. Click “Find Next” once or twice. You will get an NSD.
Can anyone confirm this? If so I will open a PMR with IBM.
Chris
Subject: Client crash reproducible (6.5.3 & 6.5.4)
I was able to reproduce this as well in 6.5.4. WinXP.
Interesting…
############################################################
FATAL THREAD 1/12 [ NLNOTES:0f48:0b3c]
FP=0x0013df50, PC=0x618265b9, SP=0x0013df44, stksize=12
EAX=0x093f13a8, EBX=0x00000182, ECX=0x00000004, EDX=0x09c20010
ESI=0x000a093f, EDI=0x000a093f, CS=0x0000001b, SS=0x00000023
DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010246
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x618265b9 nnotesws.CLineEntry::StringSearch+9 (a093f,182,13eaac,4)
@[ 2] 0x6184b583 nnotesws.CLineView::SearchLineStoreText+115 (9c20010,0,182,13eaac)
@[ 3] 0x6184b40c nnotesws.CLineView::SearchView+796 (4,182,13eaac,13e36c)
@[ 4] 0x612a6ca2 nnotesws.CLineView::ProcessMessage+2690 (182,1701be,41c,182)
@[ 5] 0x617f7d9f nnotesws.CCalendarView::ProcessMessage+3007 (9c20010,1701be,41c,182)
@[ 6] 0x6129f101 nnotesws.CViewSubprogram::SubMessageProc+497 (6d745c4,41c,182,13eaac)
@[ 7] 0x61184904 nnotesws._MainWndProc@16+6932 (1701be,41c,182,13eaac)
[ 8] 0x77d48709 USER32.GetDC+114 (61182df0,1701be,41c,182)
[ 9] 0x77d487eb USER32.GetDC+340 (0,61182df0,1701be,41c)
[10] 0x77d4b743 USER32.GetParent+364 (aa8600,86cf90,182,13eaac)
[11] 0x77d4e2f7 USER32.SendMessageA+73 (1701be,41c,182,13eaac)
@[12] 0x6134eb3e nnotesws.SendFindMessage+158 (13f12c,6134def0,0,ad010bb6)
@[13] 0x6134e3fd nnotesws.SearchWndProc+1293 (9c062e,111,8000000b,1b075a)
[14] 0x77d48709 USER32.GetDC+114 (6134def0,9c062e,111,8000000b)
[15] 0x77d487eb USER32.GetDC+340 (0,6134def0,9c062e,111)
[16] 0x77d4c00e USER32.DestroyCaret+94 (6134def0,9c062e,111,8000000b)
[17] 0x77d4c034 USER32.CallWindowProcW+27 (6134def0,9c062e,111,8000000b)
@[18] 0x61188381 nnotesws.DlgCallDefWndProc+145 (9c062e,1,1,111)
@[19] 0x61188167 nnotesws.CommonDlgProc+2375 (1,111,8000000b,1b075a)
@[20] 0x612dd561 nnotesws._MainModelessDlgProc@16+321 (9c062e,111,8000000b,1b075a)
[21] 0x77d48709 USER32.GetDC+114 (612dd420,9c062e,111,8000000b)
[22] 0x77d54ca6 USER32.CreateIconFromResourceEx+706 (0,612dd420,9c062e,111)
[23] 0x77d54af2 USER32.CreateIconFromResourceEx+270 (0,111,8000000b,1b075a)
[24] 0x77d54d1c USER32.DefDlgProcW+34 (9c062e,111,8000000b,1b075a)
[25] 0x77d48709 USER32.GetDC+114 (77d54cfa,9c062e,111,8000000b)
[26] 0x77d487eb USER32.GetDC+340 (0,77d54cfa,9c062e,111)
[27] 0x77d4b743 USER32.GetParent+364 (ac1010,9906e8,8000000b,1b075a)
[28] 0x77d4e2f7 USER32.SendMessageA+73 (9c062e,111,8000000b,1b075a)
@[29] 0x611e7770 nnotesws._SkinButtonWndProc@16+1712 (6d857c4,202,0,16003e)
[30] 0x77d48709 USER32.GetDC+114 (611e70c0,1b075a,202,0)
[31] 0x77d487eb USER32.GetDC+340 (0,611e70c0,1b075a,202)
[32] 0x77d489a5 USER32.GetWindowLongW+295 (13f7c0,0,13f744,77d6e819)
[33] 0x77d489e8 USER32.DispatchMessageW+15 (13f7c0,77d4e2ae,ea,13f7c0)
[34] 0x77d6e819 USER32.IsDialogMessageW+219 (9c062e,aacd30,0,77d4e2ae)
@[35] 0x612ce535 nnotesws.ModelessWindowDispatch+229 (9,61221c60,61180000,1)
@[36] 0x61221ea7 nnotesws._NEMMainLoop@4+583 (401000,12f0cc,15236c,0)
@[37] 0x0040156d NLNOTES._WinMain@16+1389 (400000,0,15236c,1)
@[38] 0x00401dfa NLNOTES._WinMainCRTStartup+308 (12f0cc,7c90ee18,7ffd6000,8054b038)
[39] 0x7c816d4f KERNEL32.RegisterWaitForInputIdle+73 (401cc6,0,78746341,20)
Subject: Response from IBM
IBM’s tech support spent a couple of hours on this issue. They stated that the “Ctrl-F” is actually using the OS search engine, and the problem is with the OS. So it may or may not happen depending on the OS you are using (I’m using XPSP2). The recommended workaround was to use the Notes search tool (View - Search This View). Hmmm, not the same.
They kinda just wanted to blame the OS and leave it at that, but I felt that was a cop out. I convinced them to create an SPR on the issue and have it submitted to development for review.
Good enough for me for now.
Chris
Subject: Client crash reproducible (6.5.3 & 6.5.4)
This worked for me… recieved no NSD error.
Subject: RE: Client crash reproducible (6.5.3 & 6.5.4)
No crash for me either.
Have you tried this on different mail dbs - maybe a corruption in the db?
Tony
Subject: RE: Client crash reproducible (6.5.3 & 6.5.4)
Yep, I tried it on 4 different machines. Sometimes it takes hitting “Find Next” several times before it crashes.
Subject: Client crash reproducible (6.5.3 & 6.5.4)
I am running 6.5.2 and I can recreate this crash also.
Subject: Client crash reproducible (6.5.3 & 6.5.4)
Yep, I can reproduce it on 6.5.3
Ben
Subject: Confirmed enough. I’ve opened a PMR.
I’ll post the results when I get them.