The memory leak is noticeable when using custom bone shapes. When using custom bone shapes objects could be extracted twice. Where the second
extraction can overwrite data created by the first extraction what causes the memory leak.
Options that have been checked:
- Use two task graphs phases. One for normal extraction (DST.task_graph) and the other one will handle extractions that require blocking threads.
- Keep a list of all objects that needs extraction and only start extraction when all objects have been populated.
The second would slow performance as the extraction only happens when all objects have been populated. In the future we might want to go for the second option when we have the capability to render multiple viewports with a single populate. As this design isn't clear this patch will implement the first option.