Closed ycaibb closed 3 years ago
hi @ycaibb ! i'm trying to amend it now, but there may be other stale locks, and I think split-fcc-solver is unreliable any way.
@ycaibb : hi! this commit aims to provide a symptomatic fix: https://github.com/shlomif/fc-solve/commit/934f19a754bcb0f4b292c00694e2d14e58761c53 . can this ticket be closed?
@shlomif Thanks~
@ycaibb : yw , and thanks,
Hi developers, in the below codes, the lock
instance->fcc_exit_points_output_lock
could be not released before program's exitabort();
. I think it is better to writefcs_lock_unlock(&instance->fcc_exit_points_output_lock);
before theabort();
for better resource management and code symmetry. Thanks!https://github.com/shlomif/fc-solve/blob/45efed24104b1c3ac80efb44904579d0fb238ae4/fc-solve/source/split_fcc_solver.c#L455-L478
Best,