Random NSD in DDE

HCL Domino Domino Forum
1
  • This is from a crash three days ago, April 8. Loaded the VM, called up Notes, opened a database in DDE, then went off and did other things on the host while it was loading. A short time later it simply vanished without being touched, although it did fully load and was sitting there idle:

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

thread 7/20: [ NLNOTES: 0ac0: 0c98] FATAL THREAD (Panic)

FP=0x03e8dbb4, PC=0x7c90e526, SP=0x03e8db50

stkbase=0x03e90000, total stksize=262144, used stksize=9392

EAX=0x00000000, EBX=0x03e8e784, ECX=0x00000015, EDX=0x00000000

ESI=0x000005cc, EDI=0x00000000, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x00000038, GS=0x00000000 Flags=0x00000297

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

[ 1] 0x7c90e526 ntdll.KiIntSystemCall+6 (5cc,493e0,0,3e8e364)

[ 2] 0x7c802542 kernel32.WaitForSingleObject+18 (5cc,493e0,3e8eaf8,3e8e7a3)

@[ 3] 0x601b4f65 nnotes.FRSendCommandToService+789 (3e8e384,3e8e784,3e8e7a3,0)

@[ 4] 0x601b5b9f nnotes.OSRunExternalScript@8+1055 (12c,1)

@[ 5] 0x601b611f nnotes.FRTerminateWindowsResources+975 (1,1010,1,0)

@[ 6] 0x601b6548 nnotes.OSFaultCleanupExt@24+984 (ce6a68,1010,0,0,0,3e8ee20)

@[ 7] 0x601b65ca nnotes.OSFaultCleanup@12+26 (0,1010,0)

@[ 8] 0x601c1b74 nnotes.OSNTUnhandledExceptionFilter@4+276 (3e8fe58)

@[ 9] 0x601847dd nnotes.Panic@4+589 (3e8fe70)

@[10] 0x60184894 nnotes.OSWCTPanicShutdown+84 (b1c,13a2ee8,13a57ee,3)

@[11] 0x636811a3 nnotesws.WCTShutdownThread+211 (b1c,138390,7c910041,0)

@[12] 0x6010dadf nnotes.ThreadWrapper@4+175 (0)

[13] 0x7c80b729 kernel32.GetModuleFileNameA+442 (0,0,0,0)

  • Then there is a massive chunk of stack frame dumps. This one looks important:

@[ 9] 0x601847dd nnotes.Panic@4+589 (3e8fe70)

   Parameter 1:

        03e8fe70 50726F63 65737320 6E6F7465 73322E65 | Proc ess  note s2.e |

        03e8fe80 78652028 7069643D 32383434 29206E6F | xe ( pid= 2844 ) no |

        03e8fe90 206C6F6E 67657220 65786973 74732E20 |  lon ger  exis ts.  |

        03e8fea0 41204A56 4D206661 756C7420 636F756C | A JV M fa ult  coul |

        03e8feb0 64206265 20726573 706F6E73 69626C65 | d be  res pons ible |

        03e8fec0 2E20506C 65617365 20696E73 70656374 | . Pl ease  ins pect |

        03e8fed0 20746865 20776F72 6B737061 63655C6C |  the  wor kspa ce\l |

        03e8fee0 6F677320 64697265 63746F72 7920666F | ogs  dire ctor y fo |

        03e8fef0 72206A61 76612C20 68656170 2C206F72 | r ja va,  heap , or |

        03e8ff00 20737973 74656D20 636F7265 2066696C |  sys tem  core  fil |

        03e8ff10 65732E00 00000000 94010000 00000000 | es.. .... .... .... |

        03e8ff20 94010000 C00A0000 00000000 01000000 | .... .... .... .... |
  • And little later it says it generated a core file, which is in the directory with the NSD. There is also a core file in the workspace/logs directory.

Hope this helps…