Subdivision Surface Crash #96478

Closed
opened 2022-03-15 04:46:37 +01:00 by (Deleted) · 14 comments
(Deleted) commented 2022-03-15 04:46:37 +01:00 (Migrated from localhost:3001)

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5171

Blender Version
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-03-14 00:08, hash: b959f603da
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender crashes when I set the Subdivision Surface Levels Viewport to 6.

Exact steps for others to reproduce the error

  1. Add an object (for example, Suzanne)
  2. Add a Subdivision Surface modifier and the Levels Viewport to 6 or above.

surface_subdivision_crash.blend

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5171 **Blender Version** Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-03-14 00:08, hash: `b959f603da` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender crashes when I set the Subdivision Surface Levels Viewport to 6. **Exact steps for others to reproduce the error** 1. Add an object (for example, Suzanne) 2. Add a *Subdivision Surface* modifier and the Levels Viewport to 6 or above. [surface_subdivision_crash.blend](https://archive.blender.org/developer/F12928261/surface_subdivision_crash.blend)
(Deleted) commented 2022-03-15 04:46:37 +01:00 (Migrated from localhost:3001)
Author

Added subscriber: @(Deleted)

Added subscriber: @(Deleted)
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

This is most likely caused by the GPU subdivision surface modifier introduced in Blender 3.1. Something you can do to try fix this is see if updating your GPU drivers resolves the issue.
If that doesn't help, then are you able to upload the crash log. This can be done by following these steps:

  1. Open Blender.
  2. Do the things you do to get it to crash.
  3. Find the file C:/tmp/blender.crash.txt and upload it to this site.

Are you also able to upload your system information. This can be done by following these steps:

  1. Select from the top of Blender {nav Help -> Save System Info}
  2. Upload the file saved from that to this site.

If updating your GPU drivers doesn't help then you can try disabling GPU subdivision and see if that helps. This can be done by following these steps:

  1. Select from the top of Blender {nav Edit > Preferences} and a new window will open
  2. In the preferences window, navigate to the Viewport tab.
  3. Scroll to the bottom of the Viewport tab, and in the Subdivision section disable GPU subdivision.
  4. Test again and see if Blender crashes.
This is most likely caused by the GPU subdivision surface modifier introduced in Blender 3.1. Something you can do to try fix this is see if updating your GPU drivers resolves the issue. If that doesn't help, then are you able to upload the crash log. This can be done by following these steps: 1. Open Blender. 2. Do the things you do to get it to crash. 3. Find the file `C:/tmp/blender.crash.txt` and upload it to this site. Are you also able to upload your system information. This can be done by following these steps: 1. Select from the top of Blender {nav Help -> Save System Info} 2. Upload the file saved from that to this site. --- If updating your GPU drivers doesn't help then you can try disabling GPU subdivision and see if that helps. This can be done by following these steps: 1. Select from the top of Blender {nav Edit > Preferences} and a new window will open 2. In the preferences window, navigate to the `Viewport` tab. 3. Scroll to the bottom of the `Viewport` tab, and in the `Subdivision` section disable `GPU subdivision`. 4. Test again and see if Blender crashes.
(Deleted) commented 2022-03-16 00:48:51 +01:00 (Migrated from localhost:3001)
Author

I tried going to Edit >Preferences and, the GPU Subdivision is off. So I tried to enable it and, surprisingly, Subdivision Surface seemed to work much better when I enabled GPU Subdivision. Anyways, I'll still provide the files that you want to me upload.

I tried going to **Edit** >**Preferences** and, the GPU Subdivision is off. So I tried to enable it and, surprisingly, Subdivision Surface seemed to work much better when I enabled GPU Subdivision. Anyways, I'll still provide the files that you want to me upload.
(Deleted) commented 2022-03-16 01:43:12 +01:00 (Migrated from localhost:3001)
Author

Ah, I can't find blender.crash.txt on C:/tmp/blender.crash.txt but this is the system info file.

system-info.txt

Ah, I can't find **blender.crash.txt** on **C:/tmp/blender.crash.txt** but this is the system info file. [system-info.txt](https://archive.blender.org/developer/F12929295/system-info.txt)
Member

In #96478#1323783, @SammuelProductions wrote:
Ah, I can't find blender.crash.txt on C:/tmp/blender.crash.txt but this is the system info file.

The file should be there if you follow these steps:

  1. Open Blender.
  2. Follow the steps to recreate a crash. (In your case, add an object, give it a subdivision surface modifier, set it to level 6)
  3. If Blender crashes from following the steps above, that file should be there.

If you open a file. For example cats.blend then follow the steps to get Blender to crash, then the file will be C:/tmp/cats.crash.txt

If you reboot your computer, the file will disappear.

> In #96478#1323783, @SammuelProductions wrote: > Ah, I can't find **blender.crash.txt** on **C:/tmp/blender.crash.txt** but this is the system info file. The file should be there if you follow these steps: 1. Open Blender. 2. Follow the steps to recreate a crash. (In your case, add an object, give it a subdivision surface modifier, set it to level 6) 3. If Blender crashes from following the steps above, that file should be there. If you open a file. For example `cats.blend` then follow the steps to get Blender to crash, then the file will be `C:/tmp/cats.crash.txt` If you reboot your computer, the file will disappear.

Added subscriber: @deadpin

Added subscriber: @deadpin

Windows works differently than other platforms and the crash file is written to the following per-user location:
For example with a crash here: Writing: C:\Users\jesse\AppData\Local\Temp\CrashAllObjects.crash.txt

It's also not cleared on reboot typically. You can try checking there to see if you have a crash file after you attempt things again.

Windows works differently than other platforms and the crash file is written to the following per-user location: For example with a crash here: `Writing: C:\Users\jesse\AppData\Local\Temp\CrashAllObjects.crash.txt` It's also not cleared on reboot typically. You can try checking there to see if you have a crash file after you attempt things again.
(Deleted) commented 2022-03-17 05:28:34 +01:00 (Migrated from localhost:3001)
Author

Ah, I checked on the Temp folder but I can't see subdivision_surface_crash.crash.txt. Please check the image below:Screenshot 2022-03-17 121740.png

Ah, I checked on the Temp folder but I can't see **subdivision_surface_crash.crash.txt**. Please check the image below:![Screenshot 2022-03-17 121740.png](https://archive.blender.org/developer/F12931135/Screenshot_2022-03-17_121740.png)
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member
- Run `blender_debug_log.cmd` or `blender_debug_gpu.cmd` (in same directory where blender.exe is located) - Reproduce crash on the open - Windows explorer will open with two files : upload `blender_debug_output.txt` file here Upgrade your GPU driver to the most recent one: https://docs.blender.org/manual/en/3.2/troubleshooting/gpu/windows/intel.html
Member

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Member

Reporter's account does not exist anymore. So closing this report straightaway :)

Reporter's account does not exist anymore. So closing this report straightaway :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#96478
No description provided.