Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resolve ffmpeg-triggered Windows memory usage issues #35264

Closed
goodov opened this issue Jan 11, 2024 · 0 comments · Fixed by brave/brave-core#21539
Closed

Resolve ffmpeg-triggered Windows memory usage issues #35264

goodov opened this issue Jan 11, 2024 · 0 comments · Fixed by brave/brave-core#21539
Assignees
@goodov
Labels
OS/Desktop OS/Windows perf priority/P3 The next thing for us to work on. It'll ride the trains. QA/No release-notes/exclude
Milestone
1.62.x - Release

Comments

@goodov
Copy link
Member

goodov commented Jan 11, 2024 •
edited
Loading

we cannot fallback to old ffmpeg version forever, so we need a way to use latest ffmpeg, but avoid huge memory allocations it triggers.

related #34639
@goodov goodov self-assigned this Jan 11, 2024
@goodov goodov mentioned this issue Jan 11, 2024
Merged
24 tasks
@rebron rebron added OS/Windows perf priority/P3 The next thing for us to work on. It'll ride the trains. labels Jan 11, 2024
@brave-builds brave-builds added this to the 1.63.x - Nightly milestone Jan 15, 2024
This was referenced Jan 16, 2024
Merged
Merged
@atuchin-m atuchin-m mentioned this issue Apr 9, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@goodov goodov

Labels
OS/Desktop OS/Windows perf priority/P3 The next thing for us to work on. It'll ride the trains. QA/No release-notes/exclude
Projects
None yet
Milestone
1.62.x - Release
Development

Successfully merging a pull request may close this issue.

Use dynamic allocation for ffmpeg fft tables on Windows. brave/brave-core
3 participants
@goodov @rebron @brave-builds