-
Notifications
You must be signed in to change notification settings - Fork 289
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
GPU memory not freed when using OpenCV DNN #841
Comments
Calling One option could be to use a If this works, it shouldn't require any API change and so could be included in v0.3.1. |
Looking into this some more, it is more awkward than I had realised. I had thought that wrapping everything in a Calling This makes it more of a v0.4.0 issue than a v0.3.1 issue. |
Changes were intended to fix qupath#11 However, this was only partially successful for the reasons described at qupath/qupath#841 The changes may cause complications if used with an existing `DnnModel` that lazily creates any subclass of `Pointer`, so a better solution is needed.
Aims to provide a mechanism to address * qupath#841 * qupath/qupath-extension-stardist#11 by ensuring that an OpenCV Net wrapped in a DnnModel can be closed without needing a reference to the Net itself. The StarDist and TensorFlow extensions should be updated to make use of this.
It's now possible to call |
Bug report
Describe the bug
GPU memory isn't released when using a
DnnModel
repeatedly. This can be seen when using StarDist.To Reproduce
See qupath/qupath-extension-stardist#11
Copied here because the fix may need to be implemented within the core, rather than the StarDist extension.
Expected behavior
GPU memory released after processing is complete.
Desktop (please complete the following information):
Additional context
I guess a blob may need to be reset... or something. Although that may be tricky to achieve if allowing multithreading and trying not to unduly harm performance (or perhaps it won't be).
The text was updated successfully, but these errors were encountered: