Skip to content

Fixing the SIGSEGV caused by improper termination of the internal TCP server

Petr Zejdl requested to merge fix_some_sigsegv_crashes into master

The internal TCP server was not properly terminated when the main was terminating as a result of any exception in the pipelines, causing SIGSEGV. This should handle the termination properly, without triggering SIGSEGV.

One warning: Any exception thrown in the pipelines will be only be logged, i.e. less visible, because we will not get SIGSEGV :)

Merge request reports