mattyoung101
commented
4 years ago If I recall correctly this is related to the remote debugger module, and occurs only when it's connected to Omicontrol and Omicam exits which is a rare situation (shouldn't ever happen in production).
Occasionally Omicam will segfault on exit, and ASan says it's a heap use after free, however, it got stuck printing the backtrace so I don't know where it's coming from.
Low priority because it's difficult to replicate and doesn't matter too much as it's only segfaulting on exit, after cleaning everything else up (it happens after the log file is closed too).