Designer Crash

HCL Domino Domino Forum
1

Starting today, one of our computers with Designer start to crash is a random way.

We apply all the things that we usually do to fix the issue (Compact Desktop, Repair installation, remove un-used bookmarks in the designer) and after few minutes after or just right away after calling the designer it crashed.

We downloaded the NSD Analyzer 2.7 (LND_2.7_Setup) and run it against the NSD files and the result in most of the cases is:

High number of handles (10259) for private memory block 0x0440 - BLK_SITEMAP_DATAENTRY

In the Knowledge base tab the result is:

Lotus Notes 8.5 Designer client crashes with Toolbar for Teamstudio displayed

with a link to the support document in the support database:

http://www-01.ibm.com/support

Teamstudio Analyzer was installed in that computer but never activated, so we tried to removed everything related to the product using this reference:

http://dev.kanngard.net/Permalinks/ID_20040224131727.html

However, we are still getting the computer crash with the same type of error from the NSD Analyzer.

I saw many other people with Designer Crash on this forum, and the support document is from this month so it looks like an epidemic thing.

Any ideas or suggestions on how to really remove it?

2

Subject: It is still Crashing … Teamstudio is not the bad guy!!

Just to update on this.

The NSD Analyzer always blame on Teamstudio for this type of crash, but it is not the reason.

We were able to remove Teamstudio and it was still crashing. I opened a PRM with IBM and did a brand new installation of Designer and identified that the desktop8.ndk was corrupted. After a brand new installation it crash again (NSD Analyzer still said teamstudio reference)

It crash random when a Database is selected in the desktop, you do a right click and select ‘Open in Designer’

It is possible that later you can continue working without problems until it will be impossible to start Designer.

It is not with any particular database.

I will update this with the final (if any) solution from my PRM (I send them the last NSD and the ‘corrupted’ desktop.

The critical thread is:

############################################################

FATAL THREAD 1/19 [ NLNOTES: 09c4: 09c8]

FP=0x0013b8b4, PC=0x60001a29, SP=0x0013b8a8

stkbase=00140000, total stksize=212992, used stksize=18264

EAX=0x09300332, EBX=0x091d1000, ECX=0x00000010, EDX=0x091d3f78

ESI=0x091d1000, EDI=0x09300332, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010293

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

@[ 1] 0x60001a29 nnotes.Cmovmem@12+329 (91d1040,92fbe32,7478)

@[ 2] 0x600041d4 nnotes.ODSReadMemory@16+116 (13ba70,3,92fbe32,9197478)

@[ 3] 0x6009dc02 nnotes.CSiteMapEntry::GetToolbarData+642 (877ba18,0,13daec,13dab8)

@[ 4] 0x63782763 nnotesws.CToolbarRequestHandler::WriteToolEntry+371 (4396448,877ba18,47d5618,13dd30)

@[ 5] 0x6378311e nnotesws.CToolbarRequestHandler::WriteToolbarEntry+798 (43a9d78,92f5828,47d5618,10)

3

Subject: Update after a month with an open PRM

After working back a forth with the support person in IBM and re-installing three times, sending more than 30 files of all sizes and 69 emails, we discover yesterday who was the bad guy.

It was the bookmark.nsf that was corrupted and it was not upgraded/fixed after any installation of Domino 8.5.