search

jhu-saw / sawConstraintController

4 stars 6 forks source link

Possibility of memory leaks #6

Open pwilken3 opened 9 years ago

pwilken3 commented 9 years ago

Some classes extensively use pointers (mtsVFController is a notable example) and aren't properly deleting them in the destructor. I will go through and fix these problems, but it may be worth using smart pointers instead so these problems are less likely to occur in the future. In fact, shared pointers completely negate the need for tracking "users" of kinematics and sensor objects.

pwilken3 commented 9 years ago

This problem was solved for mtsVFController, but proper destructors for kinematics and sensor objects can't be added until issue 14 is resolved.