fix: initialize tracksCacheBytes on startup to enforce cache limit (#1951)#2430
Open
fatelove42 wants to merge 1 commit intoqier222:masterfrom
Open
fix: initialize tracksCacheBytes on startup to enforce cache limit (#1951)#2430fatelove42 wants to merge 1 commit intoqier222:masterfrom
fatelove42 wants to merge 1 commit intoqier222:masterfrom
Conversation
pan93412
reviewed
Jan 18, 2026
…ier222#1951) Previously, tracksCacheBytes was initialized to 0 and only updated when entering the settings page. This caused the cache limit to not work until the user manually opened settings. Now the cache size is calculated from the database on app startup, ensuring cache cleanup triggers correctly. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Author
|
改了 |
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
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.
Previously, tracksCacheBytes was initialized to 0 and only updated when entering the settings page. This caused the cache limit to not work until the user manually opened settings. Now the cache size is calculated from the database on app startup, ensuring cache cleanup triggers correctly.
🤖 Generated with Claude Code