Skip to content

Resource Timing recovery sees only the first 250 requests #231

Closed

Description

@Nawid3333

Severity: low

Where: chrome/content.js (loadedMedia: performance.getEntriesByType('resource'), the comment "(the first 250 of them)")

What happens

Streaming pages load hundreds of ad and tracker resources before the video starts; the buffer is full before the manifest request, so LOADED_MEDIA never carries it and recovery after a background restart finds nothing but currentSrc. content.js runs at document_start, before the page's first subresource.

Suggested fix

Call performance.setResourceTimingBufferSize(2000) at document_start (one line) and, on resourcetimingbufferfull, snapshot media-looking entries into a local array before the page's own handler can clear them.

Confidence: medium.


From a line-by-line code review of the tree at 41363fd (2026-10-02). Each claim above was checked against the source before filing; the reproduction steps and line references are as of that commit.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    code-reviewFound by the 2026-10-02 line-by-line reviewenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions