Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scoped Virtual VxDataObjects are not released at time of scope release #52

Open
nashez opened this issue Nov 18, 2022 · 0 comments
Open

Comments

@nashez
Copy link

nashez commented Nov 18, 2022

In case of a virtual object, the scope for it is being updated correctly. But at the time of destruction/release of the scoped object, the VxDataObjects tied to it are not deleted.
For example, if a virtual vx_tensor is tied to a graph, then upon calling the vxReleaseGraph, the vx_tensor is not released. Same is the case for virtual vx_image objects as well.
This is causing my application to run out of memory, since my application creates multiple vx_tensors and vxProcessGraph call in a loop, even though I call vxReleaseGraph everytime in the loop.

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

No branches or pull requests

1 participant