Free image memory in Python darknet.py #6760
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
betegon
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @AlexeyAB @cenit @WongKinYiu
Following the pull request #6668 , It is a good practice to move the
free_image()call insidedetect_image()function indarknet.py. This change is suggested as it could lead to errors, as for now you have to calldetect_image()and thenfree_image()in order to detect and image.Given way I propose here, users only have to call
detect_image()to detect and image, reducing code duplication.This code has been tested and it works perfectly (it has been running detections for several hours without increasing memory usage)