# Cross Section Analysis Freezing

**URL:** <https://discourse.slicer.org/t/cross-section-analysis-freezing/37206>\
**Category:** Support\
**Tags:** python\
**Created:** [July 5, 2024, 8:02am UTC](https://discourse.slicer.org/t/cross-section-analysis-freezing/37206 "2024-07-05T08:02:31Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![SANTIAGO\_PENDON\_MING](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/santiago_pendon_ming/32/66060_2.png) [@SANTIAGO\_PENDON\_MING](https://discourse.slicer.org/u/SANTIAGO_PENDON_MING)\
**Post date:** [October 7, 2024, 11:48am UTC](https://discourse.slicer.org/t/cross-section-analysis-freezing/37206/20 "2024-10-07T11:48:29Z")

</div>

Hi @chir.set , thanks for the quick answer [here](https://discourse.slicer.org/t/run-cross-section-analysis-with-models/39561/2) .

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](https://drive.google.com/drive/folders/1ABx1OPexRbRB878qazw2ymFmHqHPZYOD?usp=sharing).

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 🙂

---

_[View the full topic](https://discourse.slicer.org/t/cross-section-analysis-freezing/37206)._