proGetStack / kill -SIGUSR1 causes memory leak, eventually crash in AppServer

OpenEdge clients leak memory if sent a SIGUSR1 signal to create protrace file
Affects all clients, including AppServer / WebSpeed agents

Also affects proGetStack script - on Linux that script just sends the SIGUSR1 signal to a PID.
Also affects other tools that rely on proGetStack script (adminServer commands such as 'asbman -agentdetail' , querying the appserver from Progress Developer Studio.)

If signal is sent often enough to same process, it crashes with SYSTEM ERROR: Memory violation. (49)

Key identifying signs of this issue:

Mapped memory regions using the agent's PID before and after running proGetStack on the agent PID, shows memory maps are not unmapped after calling proGetStack:
$   sudo cat /proc/[pid]/maps
mapped memory regions of the agents PID's grow eventually exhausting the mmap region causing the agent process terminate.

strace shows for every open('library') call there are corresponding mmap, munmap and close, execptions being /usr/lib64/libstdc++.so.6 and /lib64/libgcc_s.so.1 whose memory mappings aren't being unmapped.

Method of generating protrace files varies between operating systems; proGetStack script is a tool to make that operation platform-independent.
 

Some libraries will not be unmapped before closing the respective files.

Signal handler for SIGUSR1 initiating protrace file creation.
To create that stack trace the program calls 'backtrace' OS function, gets call stack from that and tries to map those addresses into program or external library symbol names.  In order to accomplish that, the program opens the dynamic libraries, mmaps them and then unmaps and closes them.
In some cases the unmapping of the libraries fails.

Upgrade to OpenEdge 11.6.3, 11.7 or later where library files that do not have a symbol table are unmapped properly.

Avoid sending -SIGUSR1 signals when possible.
If needed, comment out the 'kill' command within the DLC/bin/proGetStack.sh script.