Init/Wait containers exit with status code 2 and log "fatal: bad g in signal handler"

### Pre-requisites

- [X] I have double-checked my configuration
- [ ] I can confirm the issues exists when I tested with `:latest`
- [ ] I'd like to contribute the fix myself (see [contributing guide](https://github.com/argoproj/argo-workflows/blob/master/docs/CONTRIBUTING.md))

### What happened/what you expected to happen?

While executing workflow (which I can not show), I am receiving sporadically error on init/wait container in the pod which has image `argo-workflow-executor:3.3.9`

Log from containers: `fatal: bad g in signal handler`

Observing that nor the CPU is at max neither the memory on Nodes level in Grafana

### Version

v3.3.9

### Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

```YAML
Cannot add the workflow
```

### Logs from the workflow controller

No meaningful logs from `argo logs` but `argo get` is stating that тхе pod has exited with status code 2 as I have mentioned above.

### Logs from in your workflow's wait container

`fatal: bad g in signal handler`

No source file or test is named. Start by reproducing the failure with the v3.3.9 init/wait containers and a shareable workflow, then trace the signal-handler error in the executor; done means identifying a reproducible cause and demonstrating that the containers no longer exit with status 2.

Written by the indexing model from the issue text.