Delete Hierarchy operator crashes on an object whose collection is referenced by a Collection Info node with Separate Children enabled #101433
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#101433
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?
Simplified Report
Delete Hierarchy operator crashes on an object whose collection is referenced by a Collection Info node with Separate Children enabled
deleteHierarchyCrash.blend
20220928-223644.mp4
Original Report
System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94
Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash:
0759f671ce
Worked: (newest version of Blender that worked as expected)
Short description of error
Distributing instances part of a collection, enabling both the "Separate Children" checkbox in the Collection Info node and the "Hierarchy" checkbox in the Delete keymap of the Outliner, and then deleting one of the collection's objects, crashes Blender.
Exact steps for others to reproduce the error
Create a simple GN node tree with a distribute points on faces and a instances on points nodes> Use as instances a Collection of multiple objects> Enable "Separate Children" in the Collection Info node> Enable Hierarchy in the Delete keymap of the Outliner> Delete one of the collection's objects.
Bug.mp4
Bug_2.blend
blender_system_info.txt
blender_debug_output.txt
Added subscriber: @Slowwkidd
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs User Info'
I can't replicate the crash in multiple configurations. Can you not attach the file just before the crash?
There are also linked libraries that we don't have access to, could this be related?
Please open Blender's installation directory and double click on the
blender_debug_gpu.cmd
. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located inC:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt
(or simply type%TEMP%
into the path bar of the Windows Explorer).@OmarEmaraDev Done! I recreated a file (Bug_2) with factory settings and saved before the crash happened, so when open it you should find the collection info node with a collections till to assign and the checkboxes not enabled.
I opened the blend file with the debug mode and the crash happened. The new file and debug and system info texts are in the task.
The only file that I couldn't find is the crash log in temp. can't seem to find it.
Changed status from 'Needs User Info' to: 'Needs Triage'
I still can't reproduce the issue unfortunately.
Ok, I think I somehow got it, and as you presumed has to do with some addons: I have 2 addons related to geometry nodes that might be the problem, I'll update once I find out just to be sure its their fault :).
Oddly enough, it isn't what I thought: I disabled all the add-ons related to GN and also Blenderkit add-on, which in the past already was the cause of other bugs, but the bug still happens. The only time where it didn't happen was when I had a factory settings of the Preferences enabled. So, at least I can say it's something in the Preferences that's, even partially, causing it. I'll try to dive deeper, but I could determine one thing though: It's not all the checkboxes enabled it's the "Separate Children" checkbox that seems to be the trigger of the crash.
EDIT:
I think I found it: having enabled Hierarchy in the delete keymap in the Outliner is what, along with "Separate Children", causes the crash.
Deleting an instance part of a Collection used in the Collection Info node, with the checkboxes enabled, crashes Blenderto Deleting an instance part of a Collection used in the Collection Info node, with the "Separate Children" enabled, crashes BlenderDeleting an instance part of a Collection used in the Collection Info node, with the "Separate Children" enabled, crashes Blenderto Deleting an instance part of a Collection used in the Collection Info node, with "Separate Children" enabled, and "Delete Hierarchy" in the <outliner keymap enabled, crashes Blender.Deleting an instance part of a Collection used in the Collection Info node, with "Separate Children" enabled, and "Delete Hierarchy" in the <outliner keymap enabled, crashes Blender.to Deleting an instance part of a Collection used in the Collection Info node, with "Separate Children" enabled, and "Delete Hierarchy" in the Outliner keymap enabled, crashes Blender.Thanks for finding the root cause! I can confirm the issue now.
Deleting an instance part of a Collection used in the Collection Info node, with "Separate Children" enabled, and "Delete Hierarchy" in the Outliner keymap enabled, crashes Blender.to Delete Hierarchy operator crashes on an object whose collection is referenced by a Collection Info node with Separate Children enabledChanged status from 'Needs Triage' to: 'Confirmed'
Added subscribers: @JacquesLucke, @lichtwerk
I get the crash constantly here:
The IDs name for the Icoshere is something like
\000BIcosphere\000\000\...
where usually this looks likeOBIcosphere\000\000\...
When this happens,
BKE_idtype_get_info_from_id
cant determine theIDTypeInfo
(returns NULL).@JacquesLucke might now more
I hope a fix can be found in time for 3.3.1, I constantly rely on having the Delete Hierarchy option in the keymap for speeding up the process of deletion of Collections and Parents with objects.
This issue was referenced by
99c5146e9a
Changed status from 'Confirmed' to: 'Resolved'