{"record":{"id":"82e5d8180766339f","repo":"remotion-dev/remotion","slug":"light-trail-shader-compile-failed-log-no-l","errorCode":null,"errorMessage":"Light trail shader compile failed: ${log ?? '(no log)'}","messagePattern":"Light trail shader compile failed: (.+?)","errorType":"exception","errorClass":"Error","httpStatus":null,"severity":"critical","filePath":"packages/effects/src/light-trail/light-trail-runtime.ts","lineNumber":44,"sourceCode":"\tcachedColorRgba: ParsedColorRgba;\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(`Light trail 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":26,"sourceCodeEnd":62,"githubUrl":"https://github.com/remotion-dev/remotion/blob/78fe4bb3fdb5a2cd68724393d63cb223db333fa7/packages/effects/src/light-trail/light-trail-runtime.ts#L26-L62","documentation":"Thrown when the GLSL source for lightTrail fails `gl.compileShader`. The message includes the driver's info log. With a frozen, tested shader this almost always indicates a driver/compiler bug or a context that lost GPU memory mid-compile, not a user error.","triggerScenarios":"The bundled vertex/fragment shader source failing on a non-conformant driver; a context-loss or OOM during compilation causing the compiler to emit a spurious error; running on a stripped WebGL2 implementation that rejects a used extension or precision qualifier.","commonSituations":"Older Android/Chromium WebGL2 stacks; virtualized/remote GPU (RDP, old VMWare); a driver update that introduced a regression; very rare in evergreen desktop Chrome.","solutions":["Read the embedded `${log}` — it names the offending GLSL line/extension and is the primary diagnostic.","Update the GPU driver / try a different Chromium build (especially on Lambda, pin the Chrome layer).","If the log points at a precision/extension issue, report it as a @remotion/effects bug rather than working around it locally.","On context loss, dispose and re-setup after `webglcontextrestored`.","As a stopgap, disable the lightTrail effect for the affected environment."],"exampleFix":null,"handlingStrategy":"try-catch","validationCode":null,"typeGuard":null,"tryCatchPattern":"try {\n  setupLightTrail(canvas);\n} catch (err) {\n  const log = String(err?.message ?? '');\n  reportToTelemetry({ kind: 'shader-compile', log, ua: navigator.userAgent });\n  renderWithoutEffect();\n}","preventionTips":["Pin a known-good Chromium build on render workers (e.g. the Lambda Chrome layer).","Keep GPU drivers current; treat compile errors as environmental first.","Capture the shader log when surfacing the error so a fix can be targeted."],"tags":["webgl","light-trail","effects","gpu","shader"],"backgroundTag":null,"analyzedSha":"78fe4bb3fdb5a2cd68724393d63cb223db333fa7","analyzedAt":"2026-08-12T17:18:50.444Z","schemaVersion":2},"datasetVersion":"2026-08-12T18:17:37.767Z"}