Crashing during animation with Geometry Nodes ( when clicked on Attribute Randomize - Attribute field ) #89313
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#89313
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: version: 2.93, 3.0.0 Alpha, branch: master, commit date: 2021-06-18 21:33, hash:
f9aea19d98
Short description of error
Crashing during animation when using Geometry Nodes - when clicked on Attribute Randomize - Attribute field
Exact steps for others to reproduce the error
Open the file, start animation and click on the attribute search button:
scale.blend
OR:
Creating simple scene with an animation of rotating brush :
Added subscriber: @PetrSmrtka
Added subscriber: @PratikPB2123
Thanks for the report. Can you please provide a simple .blend file?
Changed status from 'Needs Triage' to: 'Needs User Info'
Added subscriber: @dfelinto
I can reproduce this with 2.93 and master. It crashes as soon as I go in the attribute search.
scale.blend
Changed status from 'Needs User Info' to: 'Confirmed'
For the records this is the bracktrace (for the main thread): P2191
Added subscribers: @JulianEisel, @HooglyBoogly
Interesting. It's use-after-free of the attribute hints. I think this is the cause:
The most straightforward solution is probably to disable attribute search when animation is playing, but this must be a relatively common problem in the UI.
@JulianEisel, is disabling the search generally the right approach?
I don't think it makes sense to disable attribute search. Although it seems harmless to do so now, it will be a problem when we have the physics clock detached from the animation clock.
Can't there just be a level of indirection, so the evaluated geometry set pointer isn't used directly? E.g. either the button gets a pointer to the pointer (so the latter can change without issues) or it gets the pointer to the owner (or the owning ID even) of the geometry set.
Added subscriber: @JacquesLucke
Just wanted to mention that tooltips are disabled as well when the animation is playing, not sure if the reasons are similar.
Given the conversation above I don't know the best solution. Now that the node UI storage is stored on the modifier, at least attribute search works now, but it still crashes when you apply an attribute, because the underlying problem is the same--
AttributeSearchData
has a pointer to an old node tree because the the UI isn't redrawn during animation.Not quite true. The pointer to the tree is fine (it's original dna data), the pointer to the
GeometryAttributeInfo
is outdated after the modifier ran again.Here is an alternative solution that does not quite work yet, but could work if we do a refactor in the ui code: P2277.
The idea is, instead of referencing
GeometryAttributeInfo
, we just copy it into the "state" of the search uibut. This way we can't get a dangling pointer.The reason this does not work yet, is because the free function passed to
UI_but_func_search_set
does not work as intended yet. We should just get rid of all thoseargN
stuff, and just always havearg
andarg_free
. This would give us much more flexibility with what we can put into auiBut
. Not sure how much of a refactor that would be.I think some of what Jacques is mentioning might make sense, and issue is still really ugly from a code architecture perspective, since this node isn't exposed anymore I don't think this needs high priority.
Well, after testing, this problem still applies in the modifier.
Still wondering why this is not an option. A pointer to the pointer should be fine if it's only the pointed to memory that is recreated.
I suppose that would work if the original ID was not reallocated during animation playback. I assumed that wouldn't be true, but maybe it is? I can look into it.
Assigning to Hans since he said he will look into it.
Don't think the original ID would be recreated then. But it may be on undo (esp. if the undone change was to the ID in question).
Okay, maybe that will work then. We'll see if undo is still an issue.
I looked into this yesterday, ended up getting frustrated battling some warnings:
I'll look into it again tomorrow.
This issue was referenced by
22ffd69a91
Changed status from 'Confirmed' to: 'Resolved'