Regression: Crash when selecting an object with an orphaned geo node link #111411
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
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
Core
Module
Development Management
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
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#111411
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.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68
Blender Version
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-10 21:29, hash:
rBca1642cd0c5c
Worked: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-09 02:25, hash:
rB756538b4a117
Short description of error
In the file that I'll attach, selecting the Cube in the Scene Collection in the View Layer immediately crashes and closes Blender.
Switching to the .blend file display, you can see orphaned node group references to another file.
These are at fault, as the geo node group "Geometry Nodes.002" from Cube used them.
The crash is associated with the geo node editor view. Changing that area to something else before clicking on the Cube doesn't crash Blender. Changing it back to the editor after clicking on the Cube crashes it.
Expected behavior
Instead of crashing, the geo node editor should just display orphaned/broken groups.
Exact steps for others to reproduce the error
Thanks for your consideration. :)
The socket drawing callback must check the node declarations to add attribute search. But the declaration may not be valid and require its updating. The callback takes a read-only node and socket. Your thoughts @HooglyBoogly (Would this kind of behavior be a safe choice) ?
Crash when selecting an object with an orphaned geo node linkto Regression: Crash when selecting an object with an orphaned geo node linkHm... caused by
1efc94bb2f
?I don't see any relation in the assertion and the only related commit for the entire bisect period...
I think updating the node declarations should be done eagerly rather than lazily, so there shouldn't be the need to do it on a
const
node. But I haven't looked into this specific issue of why the update is missing yet.