When using sbvWithAny or sbvConcurrentlyWithAny, don't use
the ThreadKilled exception to cancel solver threads once we get
a result back. If we use an async exception, it will be explicitly
filtered by the exception-handling code, leaving the solver processes
continuting to work on queries.
Instead, we throw a ExitSuccess value to the threads, which causes
them to enter their normal exception-handling stacks. This eventually
sends a termination signal to the associated solver processes before
killing the associated thread.
LeventErkok
commented
4 years ago
When using
sbvWithAnyorsbvConcurrentlyWithAny, don't use theThreadKilledexception to cancel solver threads once we get a result back. If we use an async exception, it will be explicitly filtered by the exception-handling code, leaving the solver processes continuting to work on queries.Instead, we throw a
ExitSuccessvalue to the threads, which causes them to enter their normal exception-handling stacks. This eventually sends a termination signal to the associated solver processes before killing the associated thread.Fixes #532