diff options
author | Bastien Montagne <mont29> | 2022-04-06 11:48:33 +0300 |
---|---|---|
committer | Bastien Montagne <bastien@blender.org> | 2022-04-06 12:37:15 +0300 |
commit | e06399c223686aee7c2b6f9fb2db66a5f2cffad6 (patch) | |
tree | 15779f9dd3a1cdd312c16e96db7f924aa20606ae /doc/python_api | |
parent | 8dd3387eb74566f6c52d5c83f22a8e89a908df2a (diff) |
Fix badly broken caches handling during undo/redo.
Original rework of caches during undo/redo (see D8183) had a very bad
flaw hidden in it: using the key of a ghash as source of data.
While this was effectively working then (cache pointer itself being part
of the key, and said cache pointers not being cleared on file write),
this is a general very bad way to do things.
Now that cache pointers are more and more cleared on file write (as part
of clearing runtime-data to reduce false-positives when checking if an
ID has changed or not), this has to be fixed properly by:
* Not storing the cache pointer itself in the IDCacheKey.
* In undo context, in readfile code trying to preserve caches, store the
cache pointers as values of the mapping, together with the usages counter
The first change potentially affects all usages of
`BKE_idtype_id_foreach_cache`, but in practice this code is only used by
memfile reading code (i.e. undo) currently.
Related to T97015.
Reviewed By: brecht
Maniphest Tasks: T97015
Differential Revision: https://developer.blender.org/D14559
Diffstat (limited to 'doc/python_api')
0 files changed, 0 insertions, 0 deletions