diff options
| author | Sergey Sharybin <sergey.vfx@gmail.com> | 2018-12-14 16:53:29 +0300 |
|---|---|---|
| committer | Sergey Sharybin <sergey.vfx@gmail.com> | 2018-12-14 16:53:29 +0300 |
| commit | 1e18efa1df1ad999303143156e0742d97d4c86bb (patch) | |
| tree | f96f66231abac7190084e15c1d4dd6eec3e2a367 /source/blender/blenkernel/intern/world.c | |
| parent | e54182427a41d54a900deac5b55b09a2407e31f6 (diff) | |
Fix T59220: Deleting object causes blender 2.8 to crash
The issue was caused by a special code in node tree freeing function
which will free extra fields in the case when tree is not in bmain.
This is how old code was dealing with "nested" trees, but is now
making behavior different from other datablocks. This is exactly
what was confusing copy-on-write logic.
Ideally, ntreeFreeTree() need to behave same as all other datablocks,
ad freeing of data of nested trees should be up to the owner of the
tree (this way it's all explicit and does not depend on check of
some special flag.
Diffstat (limited to 'source/blender/blenkernel/intern/world.c')
0 files changed, 0 insertions, 0 deletions