The SIGKILL coupled with your terminal emulator also being killed suggests
an OOM, out of memory, situation that causes the kernel to kill processes
to keep the entire system from dying. You're probably not correctly
initializing the state of the crypto code on subsequent calls.
On Thu, Jan 2, 202
I attached a minimal test program to reproduce an issue with
golang.org/x/crypto/argon2.
It calls IDKey twice with the same parameters. The first call executes, but
during the second call the program crashes.
Strange thing: The program does not always crash. If it crashes then I can
call it m
