Fix #110053: Crash on linked animation data with drivers #110795
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
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#110795
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ChrisLend/blender:fix_linked_driver_crash"
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?
The setup is the following
3 objects are in a source file and their collection gets linked into another file (A, B and C)
2 of those objects get a library override on their translations (A and B)
1 channel of those overrides gets a driver assigned (A) that is driven by C
(Download the files for easy testing, they are the same as on the bugreport)
Now when you link (CTRL+L) the animation data from A onto B they both appear to have the driver.
It did create a crash though when moving C because
AnimData
was anullptr
The reason it crashed is because there was no
AnimData
on the object because this lineDEG_id_tag_update(&ob_dst->ID_RECALC_TRANSFORM | ID_RECALC_GEOMETRY | ID_RECALC_ANIMATION);
was never called.
I moved the line before the check
if (ob_dst->data && ob_src->data)
to make it workFix #110053: Crash on linked animation data with driversto WIP: Fix #110053: Crash on linked animation data with driversIt seems like while during
OBJECT_OT_make_links_data
the object hasAnimData
(adt)During
BKE_animsys_eval_driver
it is anullptr
Not sure why
WIP: Fix #110053: Crash on linked animation data with driversto Fix #110053: Crash on linked animation data with driversFrom what I can tell this make it so the linked datablock is now edited, but that's not allowed.
I think the correct fix is to restructure the code so that
DEG_id_tag_update
is called?thanks for the review
changed it so the
DEG_id_tag_update
happens before theif (ob_dst->data && ob_src->data)
I'd rather restructure the code that way:
... such that it remains clear that the call to
DEG_id_tag_update
is last, after all editing changes have been performed.Not that proposed fix here is wrong, but I find it better from a logical and readability PoV. It makes the code easier to follow and safer to modify in the future.
agree that looks a lot less confusing