Maniphest T101647

Random crashes when using Snaping
Closed, Duplicate
Actions

Assigned To
None
Authored By
The5 (The5)
Oct 6 2022, 4:34 PM
Tags
  • BF Blender
Subscribers
Germano Cavalcante (mano-wii)
Massimiliano Puliero (mmaaxx)
The5 (The5)
Thomas Dinges (dingto)

Description

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.


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.txt467 KBDownload

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

Related Objects

Event Timeline

The5 (The5) created this task.Oct 6 2022, 4:34 PM
The5 (The5) updated the task description.Oct 6 2022, 4:36 PM
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Oct 6 2022, 10:09 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).

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.

Germano Cavalcante (mano-wii) mentioned this in T101747: Random crashes with GPU subdivision on some NVidea GPUs.Oct 11 2022, 6:43 PM
Massimiliano Puliero (mmaaxx) added a subscriber: Massimiliano Puliero (mmaaxx).Oct 24 2022, 3:21 AM

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

The5 (The5) added a comment.Oct 24 2022, 11:11 AM

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

Thomas Dinges (dingto) closed this task as Archived.Dec 15 2022, 4:44 PM
Thomas Dinges (dingto) added a subscriber: Thomas Dinges (dingto).

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.

Massimiliano Puliero (mmaaxx) added a comment.Dec 22 2022, 1:39 PM

The bug is still present.

The5 (The5) added a comment.Dec 22 2022, 2:08 PM

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

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

Germano Cavalcante (mano-wii) closed this task as a duplicate of T101747: Random crashes with GPU subdivision on some NVidea GPUs.Dec 22 2022, 3:25 PM