# Segment Editor crashes during Logical Operators in segment editor (Intersect) - Windows 10 - Lenovo LOQ 5.10.0

**URL:** <https://discourse.slicer.org/t/segment-editor-crashes-during-logical-operators-in-segment-editor-intersect-windows-10-lenovo-loq-5-10-0/45635>\
**Category:** Support\
**Tags:** segmentation, crash\
**Created:** [December 30, 2025, 4:30am UTC](https://discourse.slicer.org/t/segment-editor-crashes-during-logical-operators-in-segment-editor-intersect-windows-10-lenovo-loq-5-10-0/45635 "2025-12-30T04:30:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zahra\_Tabasi](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/zahra_tabasi/32/81718_2.png) [@zahra\_Tabasi](https://discourse.slicer.org/u/zahra_Tabasi)\
**Post date:** [December 30, 2025, 4:30am UTC](https://discourse.slicer.org/t/segment-editor-crashes-during-logical-operators-in-segment-editor-intersect-windows-10-lenovo-loq-5-10-0/45635/1 "2025-12-30T04:30:05Z")

</div>

**Title:** Segment Editor crashes during Logical Operators (Intersect) - Windows 10 - Lenovo LOQ

**Slicer version:** 5.10.0 (stable) + preview versions tested  
**OS:** Windows 10  
**Hardware:** Lenovo LOQ 15IRH8 (i7-13th gen, 32GB RAM, NVIDIA RTX)  
**Data:** CT chest + RTSTRUCT (3.5GB total 22 patients, but crash with single patient)

**Steps to reproduce:**

1. Load DICOM CT + RTSTRUCT (single patient)
2. Segment Editor → Logical Operators → Intersect (Heart + Field)
3. Click Apply → Immediate crash

**Error logs:**  
[Log Name: Application  
Source: Application Error  
Date: 08/10/1404 02:40:14 ب.ظ  
Event ID: 1000  
Task Category: (100)  
Level: Error  
Keywords: Classic  
User: N/A  
Computer: DESKTOP-F92USHO  
Description:  
Faulting application name: SlicerApp-real.exe, version: 0.0.0.0, time stamp: 0x6911bf2c  
Faulting module name: qSlicerBaseQTApp.dll, version: 0.0.0.0, time stamp: 0x6911bf23  
Exception code: 0xc0000005  
Fault offset: 0x0000000000005763  
Faulting process id: 0xac  
Faulting application start time: 0x01dc7913153620dd  
Faulting application path: E:\3D Slicer 5.10.0\bin\SlicerApp-real.exe  
Faulting module path: E:\3D Slicer 5.10.0\bin\qSlicerBaseQTApp.dll  
Report Id: 9b2d9262-e59a-4fae-a7da-c18098b0a6e5  
Faulting package full name:  
Faulting package-relative application ID:  
Event Xml:

1000  
0  
2  
100  
0  
0x80000000000000

3864

Application  
DESKTOP-F92USHO

SlicerApp-real.exe  
0.0.0.0  
6911bf2c  
qSlicerBaseQTApp.dll  
0.0.0.0  
6911bf23  
c0000005  
0000000000005763  
ac  
01dc7913153620dd  
E:\3D Slicer 5.10.0\bin\SlicerApp-real.exe  
E:\3D Slicer 5.10.0\bin\qSlicerBaseQTApp.dll  
9b2d9262-e59a-4fae-a7da-c18098b0a6e5

]  
[[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Session start time …: 20251229\_144023  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Slicer version …: 5.10.0 (revision 34045 / a2b6d08) win-amd64 - installed release  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Operating system …: Windows / Professional / (Build 19045, Code Page 65001) - 64-bit  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Memory …: 16108 MB physical, 37612 MB virtual  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - CPU …: GenuineIntel , 12 cores, 12 logical processors  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Qt configuration …: version 5.15.2, with SSL, requested OpenGL 3.2 (core profile)  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - DCMTK configuration …: version 3.6.8, no SSL  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Internationalization …: disabled, language=  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Developer mode …: disabled  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Application path …: E:/3D Slicer 5.10.0/bin  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۳ (unknown:0) - Additional module paths ..: [slicer.org/Extensions-34045/SlicerRT/lib/Slicer-5.10/cli-modules](http://slicer.org/Extensions-34045/SlicerRT/lib/Slicer-5.10/cli-modules), [slicer.org/Extensions-34045/SlicerRT/lib/Slicer-5.10/qt-loadable-modules](http://slicer.org/Extensions-34045/SlicerRT/lib/Slicer-5.10/qt-loadable-modules), [slicer.org/Extensions-34045/SlicerRT/lib/Slicer-5.10/qt-scripted-modules](http://slicer.org/Extensions-34045/SlicerRT/lib/Slicer-5.10/qt-scripted-modules)  
[INFO][Stream] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۴ (unknown:0) -  
[DEBUG][Python] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۵ [Python] (E:\3D Slicer 5.10.0\lib\Slicer-5.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:40) - Scripted subject hierarchy plugin registered: SegmentEditor  
[DEBUG][Python] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۵ [Python] (E:\3D Slicer 5.10.0\lib\Slicer-5.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:40) - Scripted subject hierarchy plugin registered: SegmentStatistics  
[DEBUG][Qt] ۲۹.۱۲.۲۰۲۵ ۱۴:۴۰:۲۵ (unknown:0) - Switch to module: “Welcome”  
]  
[Console output if available]

**Tried:**

- Show 3D off
- Single patient only
- Oversampling=1
- Multiple Slicer versions
- Close other apps

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [December 30, 2025, 5:59am UTC](https://discourse.slicer.org/t/segment-editor-crashes-during-logical-operators-in-segment-editor-intersect-windows-10-lenovo-loq-5-10-0/45635/2 "2025-12-30T05:59:33Z")

</div>

Windows 10 is not supported at this point. Any chance you can try this on a computer with windows 11 (to rule out that this is not a windows 10 specific problem)?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 30, 2025, 3:28pm UTC](https://discourse.slicer.org/t/segment-editor-crashes-during-logical-operators-in-segment-editor-intersect-windows-10-lenovo-loq-5-10-0/45635/3 "2025-12-30T15:28:05Z")

</div>

I could not reproduce the problem. Could you share the scene file (saved as .mrb) that you have problem with? Make sure the data is anonymized or use one of the images from Sample Data module.

---

<div class="post-metadata">

**Author:** ![zahra\_Tabasi](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/zahra_tabasi/32/81718_2.png) [@zahra\_Tabasi](https://discourse.slicer.org/u/zahra_Tabasi)\
**Post date:** [December 30, 2025, 10:41pm UTC](https://discourse.slicer.org/t/segment-editor-crashes-during-logical-operators-in-segment-editor-intersect-windows-10-lenovo-loq-5-10-0/45635/4 "2025-12-30T22:41:59Z")

</div>

**UPDATE: CRITICAL - Cannot even SAVE scene file (.mrb)**

**Original Issue:** Segment Editor → Logical Operators → Intersect → CRASH on Apply  
**NEW Issue:** Even File → Save fails BEFORE Apply!

**Error Screenshot:**

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/b/3/b30a5f9c3ac6bc571d64163e42155940c3f4e54a.png)

**Error Details:** Slicer has caught an application error, please save your work and restart. The application has run out of memory. Exception thrown in event: bad\_alloc

**Steps to reproduce:**

1. Load single patient CT + RTSTRUCT (Heart + Field segments)
2. Segment Editor → Logical Operators → Intersect (Heart ∩ Field)
3. **File → Save (.mrb)** → **CRASH before saving**
4. No Apply clicked yet!

**System:**

- Windows 10 (32GB RAM Lenovo LOQ i7)
- Slicer 5.10 stable
- Single patient only (~500MB CT)

**Notes:**

- Previously could save outputs manually
- Now crashes even on Save scene
- Tried: Close 3D view, single slice viewer

**Windows 11 VM testing tomorrow.**

**Request:** This `bad_alloc` on Save is blocking .mrb sharing.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 30, 2025, 10:54pm UTC](https://discourse.slicer.org/t/segment-editor-crashes-during-logical-operators-in-segment-editor-intersect-windows-10-lenovo-loq-5-10-0/45635/5 "2025-12-30T22:54:41Z")

</div>

This is very useful information. Your computer has simply run out of memory. If you are not working with a particularly large image then most likely there is a problem in your processing workflow that leads to unreasonably large memory need.

For example, you may have some structures that are very far out, which makes the segmentation extents extremely large. You can find the offending segment by inspecting content of the segmentation node in Data module; or delete segments and see which one you need to remove to resolve the issue. You can also force the segmentation to be stay within the reference image geometry (typically the geometry of the segmented image) by setting `Crop to reference image geometry` conversion parameter to 1.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/5/d5218e929ae3ae230e1be64805bdb8dc3bb3ffa0.png)