remotion-dev/remotion · critical · Error

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

Error message

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

What it means

A plain Error thrown by createProgram in the Liquid contours effect when gl.getProgramParameter(program, gl.LINK_STATUS) is false. The program is deleted and the info log is appended. Linking can fail even when both shaders compiled (e.g. exceeding uniform/varying limits on the device).

Source

Thrown at packages/effects/src/liquid-contours.ts:314

	}

	return shader;
};

const createProgram = (gl: WebGL2RenderingContext): WebGLProgram => {
	const vs = compileShader(gl, gl.VERTEX_SHADER, VERTEX_SHADER);
	const fs = compileShader(gl, gl.FRAGMENT_SHADER, FRAGMENT_SHADER);
	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);
	gl.deleteShader(vs);
	gl.deleteShader(fs);
	if (!gl.getProgramParameter(program, gl.LINK_STATUS)) {
		const log = gl.getProgramInfoLog(program);
		gl.deleteProgram(program);
		throw new Error(
			`Liquid contours program link failed: ${log ?? '(no log)'}`,
		);
	}

	return program;
};

const setup = (target: HTMLCanvasElement): LiquidContoursState => {
	const gl = target.getContext('webgl2', {
		premultipliedAlpha: true,
		alpha: true,
		preserveDrawingBuffer: true,
	});
	if (!gl) throw createWebGL2ContextError('liquid contours effect');
	const program = createProgram(gl);
	const vao = gl.createVertexArray();
	if (!vao) throw new Error('Failed to create WebGL vertex array');
	gl.bindVertexArray(vao);

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Read the embedded info log for the exact linker complaint.
2. Update GPU drivers / Chromium build.
3. Switch GL backend to isolate driver bugs.
4. File a Remotion issue with device, driver, and info log.

try {
  liquidContours(...);
} catch (err) {
  if (err instanceof Error && /program link failed/.test(err.message)) {
    // log info log, switch GL backend or update driver
  } else throw err;
}

When it happens

Trigger: The device compiles both Liquid contours shaders but the linker rejects the program. Shaders are static library code and user params flow through uniforms, so this is a driver/limits issue, not user input.

Common situations: Mobile/embedded GPUs with low uniform or varying limits; buggy ANGLE/D3D/Vulkan/Metal backends; outdated drivers. The info log pinpoints the cause.

Related errors

• Lines program link failed: ${log ?? '(no log)'}
• Liquid contours shader compile failed: ${log ?? '(no log)'}
• Shader compile failed: ${log ?? '(no log)'}
• Program link failed: ${log ?? '(no log)'}
• Burlap shader compile failed: ${log ?? '(no log)'}

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