Crash creating "position" attribute with the wrong type while in Edit mode #107232
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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 & 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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#107232
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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.5.0 NVIDIA 531.41
Blender Version
Broken: 3.5.0 and 3.6.0 Alpha, branch: main, commit date: 2023-04-20 23:46, hash:
5721b34e5364
Worked:
Short description of error
While in Edit mode, attempting to create an attribute called
"position"
that has type not set to"FLOAT_VECTOR"
will crash Blender.I couldn't get any other attributes to crash when added while in Edit mode.
Creating the
"position"
attribute with the correct type, but incorrect domain does not cause a crash either.I can't imagine a use case for users wanting to do this, but it came up while I was determining the extent of #107228 and isn't really the same issue.
Exact steps for others to reproduce the error
bpy.context.object.data.attributes.new("position", "FLOAT", "POINT")
from the Python Consolebpy.ops.geometry.attribute_add
operator and set theData Type
to anything other thanVector
:The crash is because positions are always accessed/treated as
CD_PROP_FLOAT3
/float3
around code [without checking], but this is not a given if we let users create "builtin" attributes with other types.@HooglyBoogly : shouldnt we really guard against creating attributes with used builtin names?
Here is another unfortunate case:
going into objectmode afterwards then makes your mesh collapse.
Does the whole issue deserve High priority?
(will raise for the moment to get the crash out of the way, feel free to lower again though...)
Yes, we should. The difference in builtin attributes between BMesh and other areas is a problem area.
You sort of have to go out of your way to do this though, which is why I didn't prioritize making it safer so far. But other perspectives make sense too.
I assume we want this bckported to 3.6 LTS @HooglyBoogly ?
Sure, couldn't hurt, it's a pretty simple change.