Hi @chir.set , thanks for the quick answer here .
The version is 3D Slicer 5.6.2 running on Window 11
The logs displayed in the slicers prompt I can’t share it because CSA blocks the interface.
The toy scene to show the questions and the problematic behaviour (for sure produced by a problematic input) is here: Scene.
The ‘bad’ segment causes ‘Waiting for background jobs’ message, meanwhile the ‘good’ segment don’t. The ‘good’ segment takes sections in the lower zone instead.
In my complete project I use segments extracted from a bigger segment and their corresponding centerlines, but if some trash appears in the segmentation the centerlines fails and can produce curves as shown in the mrb file.
Now I see clear that one possibility to freeze the module comes from the fact that I gave some bad inputs as could be in the example scene…
Are other problematic inputs (as could be give a segment that not intersects with the centerline curve) documented?
Thanks again, we think we are close to the optimal solution 