remotion-dev/remotion · error · Error

Shader compile failed: ${log ?? '(no log)'}

Error message

Shader compile failed: ${log ?? '(no log)'}

What it means

Thrown by compileShader in corner-pin-runtime.ts when gl.getShaderParameter(shader, gl.COMPILE_STATUS) is false. The CORNER_PIN_VS or CORNER_PIN_FS GLSL source failed to compile, with the info log included. Since the shader source is a library constant, this is a GPU/driver compatibility issue, not a user parameter problem.

Source

Thrown at packages/effects/src/corner-pin/corner-pin-runtime.ts:37

	};
};

const compileShader = (
	gl: WebGL2RenderingContext,
	type: number,
	source: string,
): WebGLShader => {
	const shader = gl.createShader(type);
	if (!shader) {
		throw new Error('Failed to create WebGL shader');
	}

	gl.shaderSource(shader, source);
	gl.compileShader(shader);
	if (!gl.getShaderParameter(shader, gl.COMPILE_STATUS)) {
		const log = gl.getShaderInfoLog(shader);
		gl.deleteShader(shader);
		throw new Error(`Shader compile failed: ${log ?? '(no log)'}`);
	}

	return shader;
};

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);

View on GitHub (pinned to 78fe4bb3fd)

Solutions

  1. Update GPU drivers to the latest version.
  2. Test on a different GPU/browser to isolate driver-specific issues.
  3. For headless rendering, use Chrome with full WebGL2/SwiftShader support.
  4. Report the info log and GPU details to Remotion if it reproduces on modern hardware.
Defensive patterns

Strategy: try-catch

Try / catch

try {
  cornerPin({...})(source, target);
} catch (e) {
  if (e instanceof Error && e.message.startsWith('Shader compile failed')) {
    // driver/GPU compatibility issue — capture info log from message
  }
  throw e;
}

Prevention

When it happens

Trigger: During setupCornerPin, the vertex or fragment shader fails GLSL compilation. Internal to the corner-pin WebGL pipeline — not triggered by corner pin coordinate values.

Common situations: GPU/driver lacks full GLSL ES 3.00 support despite advertising WebGL2; outdated mobile GPU drivers; browser shader-translation bug; virtual GPU with incomplete GLSL support in CI/headless rendering.

Related errors


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