fix(rrweb): aggressive blob cleanup / caching limit for safari GC#134
Closed
fix(rrweb): aggressive blob cleanup / caching limit for safari GC#134
Conversation
ksvat
force-pushed
the
safari-blob-memory-fix
branch
from
32d49ec to
0ccef6c
Compare
ksvat
requested review from
a team,
TueHaulund and
fasyy612
and removed request for
a team
Contributor
|
Closing this as the original issue was resolved |
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.
100% claude doing its thing....but i asked it for sources and it seems plausible?
Session replay causes unbounded memory growth in Safari when recording Flutter web applications, with memory increasing by ~0.5MB/second. Chrome does not exhibit this issue. Reported in
PostHog/posthog-flutter#306.
Flutter web renders the entire application UI to a full-screen <canvas> element
The canvas recording worker continuously captures frames at 4-15 FPS via OffscreenCanvas.convertToBlob(). Each call creates a Blob object that must be explicitly released.
Safari's JavaScriptCore garbage collector uses a more conservative memory management strategy compared to Chrome