Smooth Modifer Crash - TDR #76117

Closed
opened 2020-04-26 09:44:07 +02:00 by Philip Holzmann · 13 comments

System Information
Operating system: Windows 10 64 bit
Graphics card: Nvidia GTX 750 Ti

Blender Version
Broken: blender-2.83 beta 76b3aac802 or 47ae0affc8 master Fri Apr 24 11:34:04 2020 +0200

Short description of error
When the smooth modifier is applied with "crazy" values on some high poly meshes, it can crash randomly.

Checked the windows logs, and I guess a gpu timeout is what it is.

A TDR has been detected.
The application must close.

Error code: 7
 (pid=2248 tid=6436 blender.exe 64bit)

Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information.

Exact steps for others to reproduce the error
smooth01.blend
Slide the factor slider back and forth.
Sometimes it crashes immediately, sometimes it takes a few times.

**System Information** Operating system: Windows 10 64 bit Graphics card: Nvidia GTX 750 Ti **Blender Version** Broken: blender-2.83 beta 76b3aac802f9 or 47ae0affc8f29df92c82f2a9580b58f84819df7d master Fri Apr 24 11:34:04 2020 +0200 **Short description of error** When the smooth modifier is applied with "crazy" values on some high poly meshes, it can crash randomly. Checked the windows logs, and I guess a gpu timeout is what it is. ``` A TDR has been detected. The application must close. Error code: 7 (pid=2248 tid=6436 blender.exe 64bit) Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information. ``` **Exact steps for others to reproduce the error** [smooth01.blend](https://archive.blender.org/developer/F8495768/smooth01.blend) Slide the factor slider back and forth. Sometimes it crashes immediately, sometimes it takes a few times.

Added subscriber: @Foaly

Added subscriber: @Foaly

Added subscriber: @mano-wii

Added subscriber: @mano-wii

I slided the factor back and forth several times but I couldn't reproduce the crash.
Could it be that you are running out of memory?
While we want to improve Blender to handle such cases memory gracefully, this is not currently considered a bug.

I slided the factor back and forth several times but I couldn't reproduce the crash. Could it be that you are running out of memory? While we want to improve Blender to handle such cases memory gracefully, this is not currently considered a bug.

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

I got not responding situation here, pausing in debugger refused to show me anything.

I guess we could consider this known issue at least if this is caused by some "GPU hangup while process is waiting" situation that is hard to sanitize.

Though I am not sure what exactly is happening in this case.

I got not responding situation here, pausing in debugger refused to show me anything. I guess we could consider this known issue at least if this is caused by some "GPU hangup while process is waiting" situation that is hard to sanitize. Though I am not sure what exactly is happening in this case.

In #76117#919457, @iss wrote:
I got not responding situation here, pausing in debugger refused to show me anything.
...

The object being smoothed is extremely high poly, it is to be expected that the CPU takes time to compute all operations.
That's why I tested it in Release build.

> In #76117#919457, @iss wrote: > I got not responding situation here, pausing in debugger refused to show me anything. > ... The object being smoothed is extremely high poly, it is to be expected that the CPU takes time to compute all operations. That's why I tested it in Release build.

I have tested in release with debug info which usually give profiler data with no problems, but this time it gave up. also if I paused execution it showed only [external code].

I have tested in release with debug info which usually give profiler data with no problems, but this time it gave up. also if I paused execution it showed only [external code].

@iss Did it actually crash for you when not using a debugger?

Also, it occured to me to check the windows logs, and I guess a gpu timeout is what it is.

A TDR has been detected.
The application must close.

Error code: 7
 (pid=2248 tid=6436 blender.exe 64bit)

Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information.

This is unfortunate.
I believe if the smooth factor becomes too big (i.e. far greater than 1.0), the triangles become so big that they cause so many fragments to be rendered that the gpu timeouts.
I guess this could be mitigated by making 1.0 (or 2.0) a soft maximum for the factor slider, to prevent accidentally entering a huge value (which has happened to me).

@iss Did it actually crash for you when not using a debugger? Also, it occured to me to check the windows logs, and I guess a gpu timeout is what it is. ``` A TDR has been detected. The application must close. Error code: 7 (pid=2248 tid=6436 blender.exe 64bit) Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information. ``` This is unfortunate. I believe if the smooth factor becomes too big (i.e. far greater than 1.0), the triangles become so big that they cause so many fragments to be rendered that the gpu timeouts. I guess this could be mitigated by making 1.0 (or 2.0) a soft maximum for the factor slider, to prevent accidentally entering a huge value (which has happened to me).

In #76117#919767, @Foaly wrote:
@iss Did it actually crash for you when not using a debugger?

Technically not crash. but Blender become unresponsive.

Also, it occured to me to check the windows logs, and I guess a gpu timeout is what it is.

A TDR has been detected.
The application must close.

Error code: 7
 (pid=2248 tid=6436 blender.exe 64bit)

Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information.

Thanks for info.

I guess this could be mitigated by making 1.0 (or 2.0) a soft maximum for the factor slider, to prevent accidentally entering a huge value (which has happened to me).

Perhaps. I think, It is not ideal to change limits blindly if you can not guarantee that they will work.

> In #76117#919767, @Foaly wrote: > @iss Did it actually crash for you when not using a debugger? Technically not crash. but Blender become unresponsive. > Also, it occured to me to check the windows logs, and I guess a gpu timeout is what it is. > > > ``` > A TDR has been detected. > The application must close. > > Error code: 7 > (pid=2248 tid=6436 blender.exe 64bit) > > Visit http://nvidia.custhelp.com/app/answers/detail/a_id/3633 for more information. > ``` Thanks for info. > I guess this could be mitigated by making 1.0 (or 2.0) a soft maximum for the factor slider, to prevent accidentally entering a huge value (which has happened to me). Perhaps. I think, It is not ideal to change limits blindly if you can not guarantee that they will work.
Richard Antalik changed title from Smooth Modifer Crashes Randomly to Smooth Modifer Crash - TDR 2020-04-29 19:19:58 +02:00

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Brecht Van Lommel self-assigned this 2020-05-01 18:25:13 +02:00

There is not a lot we can do about TDRs, they are hard to predict and once they happen it's fully up to the graphics driver to recover from them.

GPUs are just very slow at rendering many large overlapping triangles.

There is not a lot we can do about TDRs, they are hard to predict and once they happen it's fully up to the graphics driver to recover from them. GPUs are just very slow at rendering many large overlapping triangles.
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#76117
No description provided.