search cancel

SpectroSERVER crash in libwkmgr.dll

book

Article ID: 215886

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

SpectroSERVER crashed twice. Dump files show the following information:

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffe2baf3965 (libwkmgr!CsStampedNode::~CsStampedNode+0x0000000000000209)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

PROCESS_NAME:  SpectroSERVER.exe
READ_ADDRESS:  0000000000000000 
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR:  c0000005
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000

STACK_TEXT:  
000000e6`0797fb10 00007ffe`2baf471a : 00000000`00000020 00007ffe`225b743b 0000028b`d3ab9100 00007ffe`2baf285b : libwkmgr!CsStampedNode::~CsStampedNode+0x209
000000e6`0797fb40 00007ffe`2baf4290 : 01d74a1b`ce87153c 00000000`00000000 0000028b`a69c3d80 0000028b`a69c3d80 : libwkmgr!CsWorkScheduler::get_thread+0x1e
000000e6`0797fba0 00007ffe`2baf4883 : 0000028b`a69c3d00 0000028b`a69c3d80 0000028b`a69c3d80 00000000`00000000 : libwkmgr!CsWorkScheduler::allocate_work_thread+0x34
000000e6`0797fbd0 00007ffe`256b783f : 0000028b`a6997210 00000000`00000000 00000000`00000000 00000000`00000000 : libwkmgr!CsWorkScheduler::schedule_work+0x4b
000000e6`0797fc10 00007ffe`33c1e881 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : libmoot!IOEvent::setup_fd+0x13e7
000000e6`0797fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNELBASE!BaseFiberStart+0x21

SYMBOL_NAME:  libwkmgr!CsStampedNode::~CsStampedNode+209
MODULE_NAME: libwkmgr
IMAGE_NAME:  libwkmgr.dll
STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s ; .ecxr ; kb
FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_libwkmgr.dll!CsStampedNode::_CsStampedNode
OS_VERSION:  10.0.14393.3986
BUILDLAB_STR:  rs1_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {b5374328-44e0-7781-beb6-339352d20f89}

 

Second dump shows:

 

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffe2baf3965 (libwkmgr+0x0000000000003965)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

PROCESS_NAME:  SpectroSERVER.exe
READ_ADDRESS:  0000000000000000 
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR:  c0000005
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000

IP_ON_HEAP:  0000028bdee7b1b0
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1
STACK_TEXT:  
000000e6`0797fb10 0000028b`dee7b1b0 : 00000000`00000000 ffffffff`fffffffe 00007ffe`225b5a03 0000028b`a69c3d00 : libwkmgr+0x3965
000000e6`0797fb18 00000000`00000000 : ffffffff`fffffffe 00007ffe`225b5a03 0000028b`a69c3d00 00007ffe`2baf471a : 0x0000028b`dee7b1b0

SYMBOL_NAME:  libwkmgr+3965
MODULE_NAME: libwkmgr
IMAGE_NAME:  libwkmgr.dll
STACK_COMMAND:  ~0s ; .ecxr ; kb
FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_libwkmgr.dll!Unknown
OS_VERSION:  10.0.14393.3986
BUILDLAB_STR:  rs1_release
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {6d0094c2-515b-b172-3c6c-ce5d234f03ee}

 

Environment

Spectrum 10.4.2 on Windows.

Resolution

Engineering reviewed the .dmp file and the logs provided. The crash seems to have happened when Windows failed to release a thread whose task was completed and when Spectrum tries to delete it from the thread pool the application crashes.
This seems to be a rare occurrence and the crash occurred in the very core area. Engineering doesn't see any potential problem or re-occurrence of the crash in the future.