seeing core in erlang (erl.exe) executable while shutting down rabbitMQ(3.8.14) on windows

[Pooja Desai]

Hi,

I am seeing core in erlang (erl.exe) executable while shutting down
rabbitMQ(3.8.14) on windows

Information from crash dump (including Stack trace) as below:

=====================STACK TEXT=====================================

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
.exr 0xffffffffffffffff
ExceptionAddress: 00007fff0ab64520 (beam_smp+0x0000000000004520)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
FAULTING_THREAD:  00000000000002dc
PROCESS_NAME:  erl.exe
ADDITIONAL_DEBUG_TEXT:

Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to
set symbol path and load symbols.
FAULTING_MODULE: 00007fff2c5b0000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP:  6070400f
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced
memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx
referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
READ_ADDRESS:  0000000000000000

FOLLOWUP_IP:
beam_smp+4520
00007fff`0ab64520 488b11          mov     rdx,qword ptr [rcx]
MOD_LIST: <ANALYSIS/>
BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ_WRONG_SYMBOLS
PRIMARY_PROBLEM_CLASS:  NULL_POINTER_READ
DEFAULT_BUCKET_ID:  NULL_POINTER_READ
LAST_CONTROL_TRANSFER:  from 00007fff0ab691d9 to 00007fff0ab64520
STACK_TEXT:
0000003e`8f43f420 00007fff`0ab691d9 : 0000003e`8d699340 0000003e`91705610
0000003e`925135f0 0000003e`8d591dc0 : beam_smp+0x4520
0000003e`8f43f4c0 00007fff`0ab8e2b7 : 0000003e`8df802c0 0000003e`8d442240
00000000`00000000 00007fff`0ad803bd : beam_smp+0x91d9
0000003e`8f43f6c0 00007fff`0ad81f2d : 0000003e`8cc1dbd0 00000000`00000000
0000003e`8cc1dbd0 00000000`00000000 : beam_smp+0x2e2b7
0000003e`8f43f720 00007fff`19dfcd70 : 00000000`00000000 0000003e`8df801c0
00000000`00000000 00000000`00000000 : beam_smp!sys_primitive_init+0x5bb1d
0000003e`8f43f770 00007fff`2ba713d2 : 00000000`00000000 00007fff`19dfcd30
00000000`00000000 00000000`00000000 : ucrtbase!o__realloc_base+0x60
0000003e`8f43f7a0 00007fff`2c5c54f4 : 00007fff`2ba713b0 00000000`00000000
00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x22
0000003e`8f43f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  beam_smp+4520
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: beam_smp
STACK_COMMAND:  ~4s ; kb
BUCKET_ID:  WRONG_SYMBOLS
IMAGE_NAME:  C:\PROGRA~1\xxxxxxx\erlang\erts-11.2\bin\beam.smp.dll
=====================STACK TEXT=====================================

Additional information:

I built erlang with below mentioned environment:

Packages                    Version used while building
Windows OS               -  Microsoft Windows Server 2016 Standard
Microsoft Visual Studio  -  2019 (14.27.29110)
Microsoft Windows SDK    -  SDK 10 (10.0.18362.0)
msys (64 bit)            -  msys2-x86_64-20180531
NSIS                     -  3.06.1
OpenSSL                  -  1.0.2u  - fips capable, loaded dynamically
JDK & wxWidget           -  not installed

Points to note:
* On Unix platforms we are not seeing any issue with the same build &
similar environment.

Steps referred to build erlang referred from:
https://erlang.org/doc/installation_guide/INSTALL-WIN32.html
Also, note that OTP 23.1 built with same steps & configuration is not
showing this above described crash.

Please let me know if anyone has seen a similar issue in the past or if
someone could provide me any pointers to solve this.

Thanks,
Pooja
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20210423/e15dd8b5/attachment.htm>