remotion-dev/remotion · error · Error
Light leak program link failed: ${log ?? '(no log)'}
Error message
Light leak program link failed: ${log ?? '(no log)'} What it means
Thrown by `linkProgram()` in the light-leak effect when `gl.getProgramParameter(program, gl.LINK_STATUS)` is false. The vertex and fragment shaders compiled, but linking them failed — usually a varying/uniform mismatch between stages or a driver linker bug. The driver's info log is appended.
Source
Thrown at packages/effects/src/light-leak.ts:221
};
const linkProgram = (
gl: WebGL2RenderingContext,
vs: WebGLShader,
fs: WebGLShader,
): WebGLProgram => {
const program = gl.createProgram();
if (!program) {
throw new Error('Failed to create WebGL program');
}
gl.attachShader(program, vs);
gl.attachShader(program, fs);
gl.linkProgram(program);
if (!gl.getProgramParameter(program, gl.LINK_STATUS)) {
const log = gl.getProgramInfoLog(program);
gl.deleteProgram(program);
throw new Error(`Light leak program link failed: ${log ?? '(no log)'}`);
}
return program;
};
export const lightLeak = createEffect<LightLeakEffectParams, LightLeakGlState>({
type: 'remotion/light-leak',
label: 'lightLeak()',
documentationLink: 'https://www.remotion.dev/docs/effects/light-leak',
backend: 'webgl2',
calculateKey: (params) => {
const r = resolve(params);
return `light-leak-${r.seed}-${r.hueShift}-${r.progress}`;
},
setup: (target) => {
const gl = target.getContext('webgl2', {
premultipliedAlpha: true,
alpha: true,View on GitHub (pinned to 78fe4bb3fd)
Solutions
- Reinstall `@remotion/effects` and Remotion to rule out corrupted shader source.
- Update GPU drivers and Chromium.
- Report the appended info log plus driver/Chrome versions to the Remotion tracker.
- Temporarily remove the `lightLeak()` effect to unblock the render.
Defensive patterns
Strategy: try-catch
Try / catch
try {
lightLeak({...})(...);
} catch (err) {
if (/Light leak program link failed/.test(String(err))) {
console.error('lightLeak() link failure:', String(err));
} else {
throw err;
}
} Prevention
- Reinstall @remotion/effects to rule out corrupted shader source.
- Report the appended info log to track driver linker bugs.
- Pin a known-good Chromium/GPU combo.
When it happens
Trigger: Bundled shader-pair inconsistency (varying `vUv` declared differently per stage), driver linker bug, or shader-source corruption from a broken package install.
Common situations: Driver regression; corrupted `@remotion/effects` install; unsupported Chromium; swiftshader linker limitations.
Related errors
- Levels shader link failed: ${log ?? '(no log)'}
- Light leak shader compile failed: ${log ?? '(no log)'}
- Levels shader compile failed: ${log ?? '(no log)'}
- Dot grid shader compile failed: ${log ?? '(no log)'}
- Dot grid program link failed: ${log ?? '(no log)'}
AI-assisted analysis of remotion-dev/remotion@78fe4bb3fd (2026-08-12).
Data as JSON: /api/errors/8d839fb3f249a64d.
Report an issue: GitHub.