new_from_object crash with mesh DepsgraphObjectInstance.object created from non-mesh instance_object #120145
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120145
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.33
Blender Version
Broken: version: 4.2.0 Alpha, branch: main, commit date: 2024-03-31 11:47, hash:
4855f8cd9cbe
Worked: Never (these types of mesh instances appear to have first been available in 3.0, which also crashes)
Short description of error
Converting a mesh Object from a DepsgraphObjectInstance, whose
instance_object
is not a mesh, to a new mesh withbpy.data.meshes.new_from_object
withpreserve_all_data_layers=True
crashes Blender.Exact steps for others to reproduce the error
Note that
CURVES
objects which produce mesh geometry through Geometry Nodes such asCurve to Mesh
also create a mesh object DepsgraphObjectInstance that crashes. The reproduction steps use a legacyCURVE
object because the reproduction steps are simpler.bpy.data.meshes.new_from_object crash with mesh DepsgraphObjectInstance.object created from non-mesh instance_objectto new_from_object crash with mesh DepsgraphObjectInstance.object created from non-mesh instance_objectThis happens due to
mesh->corner_data->layers == null
insculpt_multires_modifier_get
called with the instanced mesh object while trying to evaluate mesh modifiers to the final state.Not sure if any
CustomData::layers
should benull
at this stage and we can handle that inCustomData_get_active_layer_index
, or it should not be null altogether. I'm leaning towards just a null pointer handling but not sure if it will break anything else.Will try make a PR.Looks like it will still break in subsequent places. Then the
layers
should not be null.@HooglyBoogly interested in taking a look at this?
Prefer if crashes are set to High priority (could of course be lowered again if considered not severe enough)
I spent some time looking at this and didn't find anything yet. That said, the fact that the crash happens while retrieving mesh data is not really the problem but a symptom of some other larger problem in this area, which is particularly ugly.