remotion-dev/remotion · error · Error

Rings program link failed: ${log ?? '(no log)'}

Error message

Rings program link failed: ${log ?? '(no log)'}

What it means

The `rings()` effect's vertex and fragment shaders compiled but `gl.linkProgram()` failed. Because both shader stages are static constants shipped together, a link failure means the WebGL2 driver produced incompatible machine code — almost always a driver/GPU bug, a non-conformant GLSL ES 3.00 implementation, or link-time resource limits (e.g. too many varyings/uniforms) being hit on constrained hardware.

Source

Thrown at packages/effects/src/rings.ts:308

};

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(`Rings program link failed: ${log ?? '(no log)'}`);
	}

	return program;
};

const createProgram = (
	gl: WebGL2RenderingContext,
	vertexSource: string,
	fragmentSource: string,
): WebGLProgram => {
	const vs = compileShader(gl, gl.VERTEX_SHADER, vertexSource);
	const fs = compileShader(gl, gl.FRAGMENT_SHADER, fragmentSource);
	const program = linkProgram(gl, vs, fs);
	gl.deleteShader(vs);
	gl.deleteShader(fs);
	return program;
};

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Use a conformant desktop GPU with up-to-date drivers.
2. Reinstall `@remotion/effects` to rule out a patched shader source.
3. Handle context loss/restore so the program is relinked cleanly.
4. Report the `getProgramInfoLog` text plus renderer string (`WEBGL_debug_renderer_info`) to Remotion.

try {
  rings()({...});
} catch (err) {
  if (err instanceof Error && /Rings program link failed/.test(err.message)) {
    // log err.message (program info log) and render a fallback without the effect
  } else {
    throw err;
  }
}

When it happens

Trigger: Running on a non-conformant GPU/driver (older mobile, virtualized, or software rasterizer); rendering after a GPU process crash that left the context half-alive; a patched effects package whose shader source was edited so the VS/FS varyings no longer match.

Common situations: Mobile WebViews; headless render servers; remote desktop; forks of `@remotion/effects` with mismatched VS/FS edits.

Related errors

• Rings shader compile failed: ${log ?? '(no log)'}
• Roughen edges program link failed: ${log ?? '(no log)'}
• Roughen edges shader compile failed: ${log ?? '(no log)'}
• Skew program link failed: ${log ?? '(no log)'}
• Speckle program link failed: ${log ?? '(no log)'}

AI-assisted analysis of remotion-dev/remotion@78fe4bb3fd (2026-08-12). Data as JSON: /api/errors/1ef644450ff1ff03. Report an issue: GitHub.