{"record":{"id":"cd440a1f6d377390","repo":"remotion-dev/remotion","slug":"shader-compile-failed-log-no-log-cd440a","errorCode":null,"errorMessage":"Shader compile failed: ${log ?? '(no log)'}","messagePattern":"Shader compile failed: (.+?)","errorType":"exception","errorClass":"Error","httpStatus":null,"severity":"error","filePath":"packages/effects/src/chromatic-aberration/chromatic-aberration-runtime.ts","lineNumber":36,"sourceCode":"\t};\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(`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":18,"sourceCodeEnd":54,"githubUrl":"https://github.com/remotion-dev/remotion/blob/78fe4bb3fdb5a2cd68724393d63cb223db333fa7/packages/effects/src/chromatic-aberration/chromatic-aberration-runtime.ts#L18-L54","documentation":"Thrown by compileShader() in the chromatic aberration runtime when the GLSL source compiled but gl.getShaderParameter(COMPILE_STATUS) is false; the driver's info log is embedded in the message. Because the shipped CHROMATIC_ABERRATION_VS/FS are static and valid, a production compile failure almost always points to a driver/GPU bug or a degraded context, not a source error.","triggerScenarios":"gl.compileShader() at chromatic-aberration-runtime.ts:32 completes but gl.getShaderParameter reports failure at :33; the info log is read, the shader deleted, and the error at :36 is thrown with the log.","commonSituations":"Outdated/buggy GPU drivers, GPUs on the browser blocklist forced through a software fallback that rejects GLSL ES 3.00, incomplete software rasterizers, or a corrupted @remotion/effects build altering shader sources.","solutions":["Read the embedded info log to find the GLSL line the driver rejected.","Update GPU drivers to the latest stable release.","Use real GPU acceleration instead of a broken software fallback.","Reinstall/upgrade @remotion/effects to rule out shader corruption.","Reproduce on different hardware / Chrome for Testing to confirm a driver-specific bug."],"exampleFix":null,"handlingStrategy":"try-catch","validationCode":null,"typeGuard":null,"tryCatchPattern":"try {\n  return <ChromaticAberration {...props} />;\n} catch (err) {\n  const msg = String(err);\n  if (/Shader compile failed/.test(msg)) {\n  reportShaderError(msg);\n  return <FallbackFrame />;\n  }\n  throw err;\n}","preventionTips":["Keep GPU drivers current; 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.","Reproduce on Chrome for Testing to confirm hardware-specific behavior."],"tags":["webgl","glsl","shader","gpu","driver-bug","effects","chromatic-aberration","rendering"],"backgroundTag":null,"analyzedSha":"78fe4bb3fdb5a2cd68724393d63cb223db333fa7","analyzedAt":"2026-08-12T17:18:50.444Z","schemaVersion":2},"datasetVersion":"2026-08-12T18:17:37.767Z"}