Remove memory leak caused by ByteTrack #81
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
There is a memory leak in the official ByteTrack script caused by the `self.removed_stracks` variable which is allowed to grow indefinitely. This issue (&fix) was raised in the ByteTrack repo as well but the devs dont seem to be active anymore and arent reviewing pull requests. The Ultralytics yolov8 repo also had this same bug and together with their devs, we fixed it by adding these two lines which simply keep a fixed length of 100 to the history of removed tracks. This effectively fixes the memory leak without any impact on the accuracy of the tracker.
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.
Issue #, if available:
There is a memory leak in the official ByteTrack script caused by the
self.removed_stracksvariable which is allowed to grow indefinitely. This issue (&fix) was raised in the ByteTrack repo as well but the devs dont seem to be active anymore and arent reviewing pull requests.Description of changes:
The Ultralytics yolov8 repo also had this same bug and together with their devs, we fixed it by adding these two lines which simply keep a fixed length of 100 to the history of removed tracks. This effectively fixes the memory leak without any impact on the accuracy of the tracker. See here for more info.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.