tree fbfd906c00f8c7a56e0374da4c5b424e0831ce2c
parent 5a78fa8f149c63d373afb3f164d3a99f3c0f22b1
author Zane Shelley <zshelle@us.ibm.com> 1668276893 -0600
committer Zane Shelley <zshelle@us.ibm.com> 1668277878 -0600

'heap-use-after-free' error when uninitializing isolator

I found an error path in the test simulator where the Flyweight objects
are deleted before the uninitialize function is called. The default
Flyweight destructor seemed to delete all the shared pointers in
iv_index, but not actually clear out iv_index. So when the uninitialize
function called Flyweight.clear(), it tried to delete data that was
already removed from the heap. The solution was to call clear() from the
Flyweight destructor to ensure everything is deleted properly.

Change-Id: I485ce08570af7e59d9ec43cb054bce77b6866348
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>