Skip to content
This repository has been archived by the owner on Dec 22, 2024. It is now read-only.

Memory Leak in getCollidingObstacleAtConfig() #80

Open
JasonChmn opened this issue Feb 23, 2021 · 1 comment
Open

Memory Leak in getCollidingObstacleAtConfig() #80

JasonChmn opened this issue Feb 23, 2021 · 1 comment

Comments

@JasonChmn
Copy link
Contributor

There is a Memory Leak in this function.
It may be because of those pointers that are never freed when using python bindings :

char** nameList = Names_t::allocbuf(size);

Is there a way to fix it with python bindings ?

@jmirabel
Copy link
Contributor

There is no memory leak here. OmniORB takes ownership of the pointer.

This conversion code could be replaced by return hpp::corbaServer::toNames_t(res); (function from hpp-corbaserver).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants