Fix memory leak in ByteTracker #249
Open
Conversation
This file contains 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
Problem with ByteTracker during long running process. Virtual memory is consumed in same manner as memory leak. This is due to the self.removed_stracks list member variable growing without bound. The issue may be fixed by removing stale tracks from the self.removed_stracks list. A limit is placed such that tracks older that 10 * self,max_time_lost are removed from the self.removed_stracks list. This change had no discernible effect on the algorithm.
pytorch uint8 to bool for deprecation
2 tasks
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem with ByteTracker during long running process. Virtual memory is consumed in same manner as memory leak. This is due to the self.removed_stracks list member variable growing without bound. The issue may be fixed by removing stale tracks from the self.removed_stracks list. A limit is placed such that tracks older than 10 * self.max_time_lost are removed from the self.removed_stracks list. This change had no discernible effect on the algorithm.