Skip to content

🎥 Make videos programmatically with React

`@remotion/renderer`: Cap Chrome video decoder threads to prevent rendering hangs

Jonny Burgere56134ea9fc9
diff --git a/packages/renderer/src/get-video-threads-flag.ts b/packages/renderer/src/get-video-threads-flag.ts
index 7955d7d190..06832db130 100644
--- a/packages/renderer/src/get-video-threads-flag.ts
+++ b/packages/renderer/src/get-video-threads-flag.ts
@@ -4,6 +4,10 @@ import {getAvailableMemory} from './memory/get-available-memory';
const MEMORY_USAGE_PER_THREAD = 400_000_000; // 400MB
const RESERVED_MEMORY = 2_000_000_000;
+// Match Chromium's normal decoder thread limit. --video-threads bypasses that
+// limit, and too many frame threads can require more packets before producing
+// output than Mediabunny's decoder queue permits, causing frame extraction to hang.
+const MAX_VIDEO_THREADS = 16;
export const getIdealVideoThreadsFlag = (logLevel: LogLevel) => {
const freeMemory = getAvailableMemory(logLevel);
@@ -16,6 +20,7 @@ export const getIdealVideoThreadsFlag = (logLevel: LogLevel) => {
const maxRecommended = Math.min(
maxRecommendedBasedOnCpus,
maxRecommendedBasedOnMemory,
+ MAX_VIDEO_THREADS,
);
return Math.max(1, Math.round(maxRecommended));