BLI_assert failed: Delete somethink in outliner #101536
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#101536
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: Linux-5.19.7-1-MANJARO-x86_64-with-glibc2.36 64 Bits
Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01
Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-09-29 01:57, hash:
e2df195844
Worked: Error reproduced randomly, hard to find due to false negative tests
Short description of error
ASAN bactrace:
Windows crash report:
gdb-backtrace
F13611028Exact steps for others to reproduce the error
m
to move the default cube to a new collection "Collection 2"Shift-a
to add a new mesh, for example a PlaneInstance on Points
node and connect between Group Input and Group OutputCollection Info
node, and assign the collection "Collection 2" to it.Collection Info
node to theInstance
input of theInstance on Points
node.Collection 2
by selecting it and pressingx
.Cube
(which was previously inside "Collection 2") by selecting it and pressingx
.Delete crash.blend
2022-10-03 22-20-32.mp4
Added subscriber: @Valacar
Added subscriber: @mod_moder
I can confirm this with yesterday's debug build. But today I don't have it. But after that, when undo, there is still a fall. I'm downloading a newer version just to be sure.
Changed status from 'Needs Triage' to: 'Confirmed'
Thanks for your report on this.
Crash after deleting collection of Collection Info geometry nodeto BLI_assert failed: Delete somethink in outlinerAdded subscriber: @PratikPB2123
Thanks for the report. I'm not able to redo the crash. I guess this is same as #101233 (Regression: Deleting Object in outliner with a specific filter setting crashes Blender.)
Can you both confirm?
Also- It's nice to have reproducing steps written in words (video can be used as additional information)
Added subscriber: @mont29
Changed status from 'Confirmed' to: 'Needs User Info'
@Valacar @mod_moder can we please get proper bug report, following our template and guidelines (main things missing: reproducible .blend file and clear simple steps to reproduce the issue)? Thanks.
I gave what I thought was a proper bug report (steps to reproduce and a screenshot), but Illiya replaced my text with a video reproducing the bug in a slightly different way, and then later added a stack trace and blend file. It looks like my text was partially restored now. Anyway, I can confirm that the added "Delete crash.blend" attachment causes the same crash I was getting. If you delete the "Delete ME" container in the outliner and then the "Cube.001" object, it crashes. Deleting in the opposite order crashes as well. Also, as I mentioned in the steps to reproduce, you may need to do something after deleting to trigger the crash, like creating a new object in the scene.
#101233 also crashes for me, and seems related, but I'm not a developer, so I can't say if it's the same bug.
Yes, I edited your description. I pursued the goal of localizing the error as much as possible.
I tested fix #101233 in a debug build. This error is still there. Also, when the fix for that report is in the daily build, hopefully you can also check to see if it's the same bug.
I compiled a debug build of blender (
72ceb7dec1
) along with the patch from D16031 but it's still crashing (it seemed to fix #101233 though) . Debug builds don't seem to output any crash data to /tmp like a release build, so I ran it through gdb with a backtrack command after it crashed. I'll attach it here. I'm not too experienced with gdb, but hopefully it helps.#101536-gdb-backtrace.txt
Added your bug trace to the description and updated the video for an actual example file. I think the difference between a debug and a regular build is that in debug immediately see a fall, and in a normal build it only crashes when the error becomes too fatal.
Added subscriber: @lichtwerk
I havent checked on this reports, just noting that a similar thing came up in #101433 (Delete Hierarchy operator crashes on an object whose collection is referenced by a Collection Info node with Separate Children enabled)
Changed status from 'Needs User Info' to: 'Confirmed'
Added subscriber: @JacquesLucke
Thanks.
This is an issue between depsgraph and geometry nodetree I think... At least ASAN back trace shows that deleted collection is properly removed by depsgraph while rebuilding its relations, but for some reasons it looks like the object geometry, or its geonodetree, using the deleted collection is not (properly) updated... @JacquesLucke think this should be for you?
This issue was referenced by
5c42e54f6e
Changed status from 'Confirmed' to: 'Resolved'