Open chxmbley opened 5 years ago
Actually, .Call
is at the bottom of the stack trace. This is the line at the top of the trace 😕
Problem was caused by atem.ProgramInput
occasionally being nil
. Added a check in 95b9f33 to catch this.
On "connected" event program or preview input must not actually be nil. I will check it later
Occasionally,
atem.emit
panics withsignal SIGSEGV: segmentation violation
due to the.Call(in)
at this line