feat: implement max log limit with FIFO eviction#216
Open
chinecherem58 wants to merge 1 commit into
Open
Conversation
|
@chinecherem58 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
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.
Fix: Implement Max Log Limit (FIFO) to Prevent Memory Leak
Problem
The live log feed in src/app/logs/page.tsx accumulated entries indefinitely in browser memory
during long sessions, eventually crashing the tab.
Solution
This ensures the log list never exceeds 200 entries, always dropping the oldest entries first
when the limit is reached.
Testing
closes 🧹 Perf | Garbage Collection for Live Logs Feed #96