Improve frontend: only get Kernel/Journal when needed#4025
Open
joaoantoniocardoso wants to merge 5 commits into
Open
Improve frontend: only get Kernel/Journal when needed#4025joaoantoniocardoso wants to merge 5 commits into
joaoantoniocardoso wants to merge 5 commits into
Conversation
joaoantoniocardoso
added
the
move-to-stable
joaoantoniocardoso
requested review from
Williangalvani,
joaomariolago,
nicoschmdt and
patrickelectric
July 24, 2026 22:22
This comment was marked as resolved.
This comment was marked as resolved.
…bSocket subscribe API Stop opening kernel and journal WebSockets (and the journal REST fetch) at SPA boot. Expose subscribe/unsubscribe helpers that open sockets on demand and clear buffers when the last consumer leaves.
…om tab views Open the lazy WebSocket subscriptions when Kernel and Journal mount, and unsubscribe (clearing buffers) on destroy.
Only mount the selected tab content so Kernel/Journal tear down their WebSocket subscriptions when leaving those tabs (Vuetify otherwise keeps visited tab components alive).
v-tabs uses a numeric index and the active-tab v-if compares against numbers; start at 0 so the first tab mounts immediately.
…al REST paths Kernel and journal data now come only from the lazy WebSocket subscribers; drop the orphan FetchType cases, mutations, and fetchKernelMessage action.
joaoantoniocardoso
force-pushed
the
fix_frontend_deterioration_over_time
branch
from
July 24, 2026 22:50
bf350a5 to
4ec2df0
Compare
joaoantoniocardoso
marked this pull request as draft
July 24, 2026 22:58
joaoantoniocardoso
marked this pull request as ready for review
July 24, 2026 22:58
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
1 participant
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.
During my tests, it was found that there's an initial ~22 + linear ~5 MB/h of Chrome heap growth just from Journal+Kernel, regardless of the page loaded. This certainly is not the single or greatest cause of instability, but can be a contributor.
The strategy here is to only connect the WebSocket when we need it, which is not even common.
Note: In 1.4, we only have the Kernel ones, so this can be a contributor to why the 1.5 frontend is heavier than 1.4.