# App quit while operating on big volume

**URL:** https://discourse.slicer.org/t/app-quit-while-operating-on-big-volume/24720
**Category:** Support
**Created:** [August 11, 2022, 8:12pm UTC](https://discourse.slicer.org/t/app-quit-while-operating-on-big-volume/24720 "2022-08-11T20:12:20Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![allenzhuang975](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/allenzhuang975/32/16285_2.png) [@allenzhuang975](https://discourse.slicer.org/u/allenzhuang975)
#### Post date: [August 11, 2022, 8:12pm UTC](https://discourse.slicer.org/t/app-quit-while-operating-on-big-volume/24720/1 "2022-08-11T20:12:20Z")

</div>

Problem report for Slicer 5.0.3 win-amd64: [please describe expected and actual behavior]

Volume was about 674 x 674 x 1974. When I rotating the volumes in the cener windows, the app crushed, and every time. It takes up about 5G memory.

[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Session start time …: 2022-08-11 11:50:35  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Slicer version …: 5.0.3 (revision 30893 / 7ea0f43) win-amd64 - installed release  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Operating system …: Windows / Personal / (Build 19044, Code Page 65001) - 64-bit  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Memory …: 20362 MB physical, 30362 MB virtual  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - CPU …: GenuineIntel , 8 cores, 8 logical processors  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Qt configuration …: version 5.15.2, with SSL, requested OpenGL 3.2 (compatibility profile)  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Internationalization …: disabled, language=  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Developer mode …: disabled  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Application path …: E:/Users/admin/AppData/Local/NA-MIC/Slicer 5.0.3/bin  
[DEBUG][Qt] 11.08.2022 11:50:35 (unknown:0) - Additional module paths …: (none)  
[DEBUG][Python] 11.08.2022 11:50:37 [Python] (E:\Users\admin\AppData\Local\NA-MIC\Slicer 5.0.3\lib\Slicer-5.0\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:38) - Scripted subject hierarchy plugin registered: Annotations  
[DEBUG][Python] 11.08.2022 11:50:37 [Python] (E:\Users\admin\AppData\Local\NA-MIC\Slicer 5.0.3\lib\Slicer-5.0\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:38) - Scripted subject hierarchy plugin registered: SegmentEditor  
[DEBUG][Python] 11.08.2022 11:50:37 [Python] (E:\Users\admin\AppData\Local\NA-MIC\Slicer 5.0.3\lib\Slicer-5.0\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:38) - Scripted subject hierarchy plugin registered: SegmentStatistics  
[DEBUG][Qt] 11.08.2022 11:50:38 (unknown:0) - Switch to module: “Welcome”

---

<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: [August 11, 2022, 8:17pm UTC](https://discourse.slicer.org/t/app-quit-while-operating-on-big-volume/24720/2 "2022-08-11T20:17:03Z")

</div>

If the application crashed while rotating a volume rendered image in the 3D view then it means that your GPU took too long time to render an image (caused a TDR error) and so Windows terminated the application. You have many options to resolve the issue as described in this post:

> [@Enabling volume rendering for a large volume makes the application crash](https://discourse.slicer.org/t/enabling-volume-rendering-for-a-large-volume-makes-the-application-crash/17032/7):
>
> This indicates that you get a TDR error: the operating system shuts down applications that keep the graphics card busy for too long. This happens because the size of the volume is too large for your GPU to comfortably handle. There are several ways to work around this: Option A: Run the code snippet above to split the volume to smaller chunks (that way you have a better chance that the graphics card will not be unresponsive for too long) or increase TDR delay in the registry. Option B: Crop a…

---

<div class="post-metadata">

### Author: ![allenzhuang975](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/allenzhuang975/32/16285_2.png) [@allenzhuang975](https://discourse.slicer.org/u/allenzhuang975)
#### Post date: [August 12, 2022, 3:12am UTC](https://discourse.slicer.org/t/app-quit-while-operating-on-big-volume/24720/3 "2022-08-12T03:12:41Z")

</div>

> [@Enabling volume rendering for a large volume makes the application crash](https://discourse.slicer.org/t/enabling-volume-rendering-for-a-large-volume-makes-the-application-crash/17032/7):
>
> TDR delay

Thank you for your reply. After I have done the following, it seems to work.

1. Set DWORD value 0x10 named TdrDelay at path : HKLM\System\CurrentControlSet\Control\GraphicsDriver\

2. Restarted Windows 10,
