Crash when unloading a scene with pynodes and idprop of type id #61515
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#61515
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?
Blender Version
Broken:
c6e3a20ab6
Exact steps for others to reproduce the error
File -> New -> General
-> Crash.Added subscriber: @JacquesLucke
Added subscriber: @ZedDB
@JacquesLucke I can not reproduce this on my end (
74a3d9b410
)This issue was referenced by
a4e81e2dfb
File->new triggers a "Main nuke", which means we do not clean up properly every IDs, and count on order in which ID types are freed to save us from that kind of issue.
But freeing code of each ID type should not do any ID refcounting management either, yet another bug in NT code. :|
@ZedDB, maybe in a debug build?
@ZedDB with an ASAN build on linux, this should always lead to an hard crash with heavy complains of 'using memory after free' ;)
Changed status from 'Open' to: 'Resolved'
Ok, I guess it doesn't crash because my current build is a Debug build but without ASAN.
@mont29, why is it so important to have all these special cases for node trees? Couldn't we just take the nodetree from a material and put it in bmain as well?
Or we define another type that contains all the nodes but is not an ID. This type can then be used by materials/textures/... But it can also be a part of
bNodeTree
which is an ID.I'm sure this idea what is not new, but could you repeat the reasoning why we don't do it this way for me, please?
@JacquesLucke yes, that something like that that should have been made from the start. But no, people like to complicate things at global level, just for the sake of some immediate, localized simplification… Thing is, doing that now is not trivial at all, given the plate of spaghetti that is NodeTree code. Would involve a lot of careful checking and testing to ensure nothing gets broken on the way. Never had the courage to dive really into this. :|
Note that same mistake was done again in 2.8 with collections (master collections of scenes are not in Main database). :'((((
@mont29, I see, thanks. That's sad...