When you hit CALL, the stack-group that was running is unwound in the keyboard process rather than in its own process. If it had locks locked, an error-check in PROCESS-UNLOCK goes off spuriously. I don't think just taking out the error check is the right solution.