Customer reported issue with ProcMgr crashing on a idle system with 8 modules configured.
Analysis showed a lot of getactivealarm commands were being process by ProcMgr at the same time and these request was coming from the 8 ServerMonitors on the system.

I was able to create the crash on my setup just at an idle state, but did when I ran the following script from pm5, which send alot of getactivealarm request to ProcMgr

#!/bin/bash
while [ true ]; do
/home/mariadb-user/mariadb/columnstore/bin/mcsadmin getactivea
done
exit 0

2715 Thread 0x7ff4effff700 (LWP 5932) "ProcMgr" 0x00007ff57a09666d in nanosleep () from /lib64/libc.so.6
2714 Thread 0x7ff507fff700 (LWP 5931) "ProcMgr" 0x00007ff57a09666d in nanosleep () from /lib64/libc.so.6
--Type <return> to continue, or q <return> to quit--q
Quit
(gdb) bt
#0 0x00007ff57a00d1d7 in raise () from /lib64/libc.so.6
#1 0x00007ff57a00e8c8 in abort () from /lib64/libc.so.6
#2 0x00007ff57a9119d5 in _gnu_cxx::_verbose_terminate_handler() () from /lib64/libstdc++.so.6
#3 0x00007ff57a90f946 in ?? () from /lib64/libstdc++.so.6
#4 0x00007ff57a90f973 in std::terminate() () from /lib64/libstdc++.so.6
#5 0x00007ff57a90fb93 in __cxa_throw () from /lib64/libstdc++.so.6
#6 0x00007ff57c35ad44 in messageqcpp::ByteStream::peek (this=0x7ff489ff8460, s="")
at /home/builder/mariadb-columnstore-server/mariadb-columnstore-engine/utils/messageqcpp/bytestream.cpp:416
#7 0x00007ff57c35a45b in messageqcpp::ByteStream::operator>> (this=0x7ff489ff8460, s="")
at /home/builder/mariadb-columnstore-server/mariadb-columnstore-engine/utils/messageqcpp/bytestream.cpp:310
#8 0x00000000004605bb in processmanager::processMSG (cfIos=0x7ff56bffeab0)
at /home/builder/mariadb-columnstore-server/mariadb-columnstore-engine/procmgr/processmanager.cpp:2743
#9 0x00007ff57adc9dc5 in start_thread () from /lib64/libpthread.so.0
#10 0x00007ff57a0cf73d in clone () from /lib64/libc.so.6