fatal error: all goroutines are asleep - deadlock!

[rchikhi]

I've had gotranseq randomly crash with this error. Used current master branch and parameters --frame 6 and -n 1, if that matters. Crash does not appear to be deterministic: re-ran the tool on the same file and it went fine. Could be related with -n 1 not being enforced sometimes, as CPU usage can be >100%.

[feliixx]

Hi @rchikhi, interresting thanks for reporting this.

Could be related with -n 1 not being enforced sometimes, as CPU usage can be >100%.

The -n/-numcpu flag is confusing, as under the hood it doesn't garantee that only one CPU will be used. In reality it means that n workers (= goroutine in go) will be launched to translate the file in parralel, and the amount of proccessing power used by each worker depends on the go runtime.

I'll try to fuzz the tool with -n 1 to see if I can reproduce the issue