Random crashes when using Snaping #101647

Closed
opened 2022-10-06 16:34:11 +02:00 by The5 · 13 comments

System Information
Operating system: Windows 10
Graphics card: RTX 3090 516.94

Blender Version
Broken: 3.3.0
Worked: ---

Short description of error
When using Snapping, blender crashes occasionally but without any identifiable pattern.
It seems to have started occurring to me in 3.3.0 and worked in 3.2.0 (or at least it was not frequent enough for me to be bothered by it).

Exact steps for others to reproduce the error
The crash occurs randomly and I found no way to reliably reproduce it yet.

Using the following snapping settings to snap the selected object to the surface of another object.
blender_snap_crash.JPG
The selected/active object that is snapped onto the surface usually is a freshly created primitive.
The object that shall be snapped to is usually a complex mesh with modifiers like subdivisions, mirror, solidify, bevel and booleans.
The mesh that I suspect caused the crash on hovering over it has mirror, subdiv, 2nd subdiv, 4x boolean, mirror and after modifiers about 130k triangles.

Most recent crash log:
F_PMS_Jaguar_custom.crash.txt
The backtrace begins after spawning in a circle object, then holding CTRL and moving the cursor onto my target mesh.
It seems to occur in OpenSubdiv, which would make sense given my target snapping objects are usually subdivided.
I often have two subdivision modifiers on my objects and noticed severe slowdowns when editing a mesh with two of them rather than one.
Maybe that is related?

https://developer.blender.org/T96367 seems related but is apparently fixed

**System Information** Operating system: Windows 10 Graphics card: RTX 3090 516.94 **Blender Version** Broken: 3.3.0 Worked: --- **Short description of error** When using Snapping, blender crashes occasionally but without any identifiable pattern. It seems to have started occurring to me in 3.3.0 and worked in 3.2.0 (or at least it was not frequent enough for me to be bothered by it). **Exact steps for others to reproduce the error** The crash occurs randomly and I found no way to reliably reproduce it yet. Using the following snapping settings to snap the selected object to the surface of another object. ![blender_snap_crash.JPG](https://archive.blender.org/developer/F13623385/blender_snap_crash.JPG) The selected/active object that is snapped onto the surface usually is a freshly created primitive. The object that shall be snapped to is usually a complex mesh with modifiers like subdivisions, mirror, solidify, bevel and booleans. The mesh that I suspect caused the crash on hovering over it has mirror, subdiv, 2nd subdiv, 4x boolean, mirror and after modifiers about 130k triangles. Most recent crash log: [F_PMS_Jaguar_custom.crash.txt](https://archive.blender.org/developer/F13623392/F_PMS_Jaguar_custom.crash.txt) The backtrace begins after spawning in a circle object, then holding CTRL and moving the cursor onto my target mesh. It seems to occur in OpenSubdiv, which would make sense given my target snapping objects are usually subdivided. I often have two subdivision modifiers on my objects and noticed severe slowdowns when editing a mesh with two of them rather than one. Maybe that is related? https://developer.blender.org/T96367 seems related but is apparently fixed
Author

Added subscriber: @The5

Added subscriber: @The5

Added subscriber: @mano-wii

Added subscriber: @mano-wii

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

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

Thanks for the report,

Please be sure to provide the simplified .blend file which we can use to reproduce the bug.
If the file is very large or complex, try simplifying it.
Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

Thanks for the report, Please be sure to provide the simplified .blend file which we can use to reproduce the bug. If the file is very large or complex, try simplifying it. Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

Added subscriber: @MassimilianoPuliero

Added subscriber: @MassimilianoPuliero

Hi all,

I'm pretty sure that this happens only with the "GPU Subdivision" option is activated.
By turning it off the snapping is way faster and never crashed once in 2 hours of work.

Hope this help

Max

Hi all, I'm pretty sure that this happens only with the "GPU Subdivision" option is activated. By turning it off the snapping is way faster and never crashed once in 2 hours of work. Hope this help Max
Author

Thanks, I'll give it a go with GPU Subdiv disabled and report back!

Thanks, I'll give it a go with GPU Subdiv disabled and report back!

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

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

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

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

The bug is still present.

The bug is still present.
Author

I still found no way to reproduce it, it remains random.

That said, I have not observed a crash with GPU subdiv off.

I still found no way to reproduce it, it remains random. That said, I have not observed a crash with GPU subdiv off.

Closed as duplicate of #101747

Closed as duplicate of #101747
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#101647
No description provided.