Can KILL -SIGUSR1 cause a process to crash?

Can kill -SIGUSR1 cause an OpenEdge process to crash with SE 49?
Can running proGetStack.sh cause a process to crash on Unix or Linux ?
Can SIGUSR1 signals sent to a client process cause a DBDOWN?

kill -SIGUSR1 is used on Unix/Linux systems to trigger an ABL client process to generate a protrace file

When a process that receives a -SIGUSR1 request to dump a stack and also receives a simultaneous interrupt signal, the process can end up crashing with SYSTEM ERROR 49 which may also bring the database down as a result, or the process will hang indefinitely and no longer be responsive to further interrupt signals.

The cause has been identified in async unsafe calls in signal handling as an ongoing investigation which have been addressed in separate defects:

Upgrade to OpenEdge 11.6.4, 11.7 or later where all known issues associated with async unsafe signal handling have been addressed by implementing alternative functions, which are safe with asynchronous signal handling:

•  OpenEdge processes sometimes hang or crash after receiving HANGUP or USR1 signal 
•  ABL client hangs. Protrace shows malloc function making subcall to malloc on Linux.

Should any further incidents occur in later versions, please open a support case with technical support along with a reproducible (if possible) to be pursued as a defect. 

Progress Articles:

 OpenEdge processes sometimes hang or crash after receiving HANGUP or SIGUSR1  
 proGetStack causes memory leak in AppServer