{"record":{"id":"06f9e3a5b7b86bdf","repo":"remotion-dev/remotion","slug":"checkerboard-shader-compile-failed-log-no","errorCode":null,"errorMessage":"Checkerboard shader compile failed: ${log ?? '(no log)'}","messagePattern":"Checkerboard shader compile failed: (.+?)","errorType":"exception","errorClass":"Error","httpStatus":null,"severity":"error","filePath":"packages/effects/src/checkerboard.ts","lineNumber":287,"sourceCode":"}\n`;\n\nconst compileShader = (\n\tgl: WebGL2RenderingContext,\n\ttype: number,\n\tsource: string,\n): WebGLShader => {\n\tconst shader = gl.createShader(type);\n\tif (!shader) {\n\t\tthrow new Error('Failed to create WebGL shader');\n\t}\n\n\tgl.shaderSource(shader, source);\n\tgl.compileShader(shader);\n\tif (!gl.getShaderParameter(shader, gl.COMPILE_STATUS)) {\n\t\tconst log = gl.getShaderInfoLog(shader);\n\t\tgl.deleteShader(shader);\n\t\tthrow new Error(`Checkerboard shader compile failed: ${log ?? '(no log)'}`);\n\t}\n\n\treturn shader;\n};\n\nconst linkProgram = (\n\tgl: WebGL2RenderingContext,\n\tvs: WebGLShader,\n\tfs: WebGLShader,\n): WebGLProgram => {\n\tconst program = gl.createProgram();\n\tif (!program) {\n\t\tthrow new Error('Failed to create WebGL program');\n\t}\n\n\tgl.attachShader(program, vs);\n\tgl.attachShader(program, fs);\n\tgl.linkProgram(program);","sourceCodeStart":269,"sourceCodeEnd":305,"githubUrl":"https://github.com/remotion-dev/remotion/blob/78fe4bb3fdb5a2cd68724393d63cb223db333fa7/packages/effects/src/checkerboard.ts#L269-L305","documentation":"Thrown by compileShader() for the checkerboard effect when the GLSL source compiles but gl.getShaderParameter(shader, COMPILE_STATUS) is false. The message embeds the driver's info log. Because the shipped CHECKERBOARD_VS/CHECKERBOARD_FS are static and well-formed, a compile failure in production almost always indicates a driver/GPU bug or a context in a degraded state rather than a source error.","triggerScenarios":"gl.compileShader() at checkerboard.ts:283 completes but gl.getShaderParameter reports failure at :284; the info log is read, the shader is deleted, and the error at :287 is thrown with the log embedded.","commonSituations":"Buggy/outdated GPU drivers, GPU blacklisted with a fallback that rejects ES 3.00 (#version 300 es), software rasterizers with incomplete GLSL ES 3.00 support, or a corrupted shader string from a tampered/older build of @remotion/effects.","solutions":["Read the embedded info log in the error message — it names the exact GLSL line the driver rejected.","Update GPU drivers to the latest stable release.","Ensure the browser is using real GPU acceleration, not a broken software fallback.","Reinstall/upgrade @remotion/effects to rule out a corrupted shader string.","Try a different GPU or a headed Chromium (e.g. Chrome for Testing) to isolate driver-specific bugs."],"exampleFix":null,"handlingStrategy":"try-catch","validationCode":null,"typeGuard":null,"tryCatchPattern":"try {\n  return <Checkerboard {...props} />;\n} catch (err) {\n  const msg = String(err);\n  if (/Checkerboard shader compile failed/.test(msg)) {\n  // surface the embedded info log to ops; fall back to no-effect frame\n  reportShaderError(msg);\n  return <FallbackFrame />;\n  }\n  throw err;\n}","preventionTips":["Keep GPU drivers up to date; shader compile failures on shipped GLSL are usually driver bugs.","Avoid software rasterizers with incomplete GLSL ES 3.00 support.","Pin and verify the installed @remotion/effects version so shader sources are not corrupted.","Reproduce on Chrome for Testing to confirm hardware-specific behavior."],"tags":["webgl","glsl","shader","gpu","driver-bug","effects","checkerboard","rendering"],"backgroundTag":null,"analyzedSha":"78fe4bb3fdb5a2cd68724393d63cb223db333fa7","analyzedAt":"2026-08-12T17:18:50.444Z","schemaVersion":2},"datasetVersion":"2026-08-12T23:17:12.415Z"}