Exception on deleting a child in Model Explorer
Posted: Thu May 01, 2025 2:54 am
This is a re-post of the issue reported by oliver_h in the Memory issues loading in stl files.. thread:
"
One interesting thing (which may not be related) I ran into: When running the code with SeparateObjects, the tree view in the model explorer contains one root node named "Component", with two child nodes named "Child_0" and "Child_1" (as you'd expect). If in the model explorer you delete Child_0 and then Child_1 they delete as expected (although without freeing memory). However, if you delete Child_1 while there is still a Child_0, the program crashes with the following message: (Access Violation Exception).
"
The problem is unrelated to the thread and deserves its own.
"
One interesting thing (which may not be related) I ran into: When running the code with SeparateObjects, the tree view in the model explorer contains one root node named "Component", with two child nodes named "Child_0" and "Child_1" (as you'd expect). If in the model explorer you delete Child_0 and then Child_1 they delete as expected (although without freeing memory). However, if you delete Child_1 while there is still a Child_0, the program crashes with the following message: (Access Violation Exception).
"
The problem is unrelated to the thread and deserves its own.