Skip to content

Bound setMediaStream search to the trak atom size (backport #9286)#9319

Merged
kmilos merged 6 commits into
0.28.xfrom
mergify/bp/0.28.x/pr-9286
Jun 15, 2026
Merged

Bound setMediaStream search to the trak atom size (backport #9286)#9319
kmilos merged 6 commits into
0.28.xfrom
mergify/bp/0.28.x/pr-9286

Conversation

@mergify

@mergify mergify Bot commented May 29, 2026

Copy link
Copy Markdown
Contributor

Fix #9285:

setMediaStream() scans for "hdlr" in a while(!eof) loop with no size bound. When a file has no "hdlr" atom in the expected position, the loop reads through the entire rest of the file.

Pass the trak atom size and stop the search at that boundary.


This is an automatic backport of pull request #9286 done by Mergify.

MarkLee131 and others added 6 commits May 29, 2026 23:04
setMediaStream() scans for "hdlr" in a while(!eof) loop with no
size bound. When a file has no "hdlr" atom in the expected
position, the loop reads through the entire rest of the file.

Pass the trak atom size and stop the search at that boundary.

(cherry picked from commit b5cb228)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
(cherry picked from commit fd3f4fb)
Co-authored-by: Kevin Backhouse <kevinbackhouse@github.com>
(cherry picked from commit ee13a61)
Co-authored-by: Kevin Backhouse <kevinbackhouse@github.com>
(cherry picked from commit 44b9b7d)
Co-authored-by: Kevin Backhouse <kevinbackhouse@github.com>
(cherry picked from commit 02d5e63)
@kmilos kmilos merged commit 5eeaafc into 0.28.x Jun 15, 2026
86 of 91 checks passed
@kmilos kmilos deleted the mergify/bp/0.28.x/pr-9286 branch June 15, 2026 10:30
@kmilos kmilos added this to the v0.28.9 milestone Jun 15, 2026
@kmilos

kmilos commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

@kevinbackhouse I was maybe too quick to merge this, sorry - changes the API, so not for 0.28.9 in fact, just like #9333?

@kevinbackhouse

Copy link
Copy Markdown
Collaborator

@kevinbackhouse I was maybe too quick to merge this, sorry - changes the API, so not for 0.28.9 in fact, just like #9333?

Good catch! I agree, probably safer to revert this and include it in 0.29.0 instead.

@kmilos kmilos removed this from the v0.28.9 milestone Jun 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants