"Error:SVG data parsing failed cause unknown token" when running on standalone server

[Tonyce]

Error: failed to pipe responseat pipeToNodeResponse(/app/node_modules/.pnpm/next@14.2.3 reac
at async sendResponse(/app/node modules/.pnpm/next@14.2.3 reac
at async doRender (/app/node modules/.pnpm/next@14.2.3 react-dor
at async cacheEntry.responseCache.get.routeKind(/app/node_modu
at async NextNodeServer.renderToResponseWithComponentsImpl (/ap
at async NextNodeServer.renderPageComponent (/app/node_modules/
at async NextNodeServer.renderToResponseImpl (/app/node_modules.
at async NextNodeServer.pipeImpl (/app/node_ modules/.pnpm/next@
at async NextNodeServer.handleCatchallRenderRequest (/app/node.
at async NextNodeServer.handleRequestImpl (/app/node modules/.p!Icause]: Error:SVG data parsing failed cause unknown token at 1:at imports.wbg.wbg new 15d3966e9981a196(file:///app/node mo
at wasm://wasm/005420d6:wasm-function[515]:0x112c4cat wasm://wasm/005420d6:wasm-function[30]:0x3ffde

[stephancill]

Hi, please share a reproducible example or the frame route that you are seeing this error on

[Tonyce]

https://github.com/Tonyce/frames-debug . Keep requesting /frames/image and you will get this error

[stephancill]

thanks for providing the repo. i'm unable to run it - can't request /frames/images directly and /frames requires some external API access

[stephancill]

Turns out @vercel/og has a memory leak that doesn't manifest itself in serverless contexts. The workaround is to patch the @vercel/og package in your project - see the necessary changes in this comment thx/resvg-js#216 (comment)

Here is the an exact diff for @vercel+og+0.6.2

diff --git a/node_modules/@vercel/og/dist/index.node.js b/node_modules/@vercel/og/dist/index.node.js
index c92983c..a516f4f 100644
--- a/node_modules/@vercel/og/dist/index.node.js
+++ b/node_modules/@vercel/og/dist/index.node.js
@@ -18786,7 +18786,11 @@ async function render(satori2, resvg, opts, defaultFonts, element) {
       value: options.width
     }
   });
-  return resvgJS.render().asPng();
+  const pngData = resvgJS.render();
+  const pngBuffer = pngData.asPng();
+  pngData.free();
+  resvgJS.free();
+  return pngBuffer;
 }
 
 // src/figma/index.tsx

[dalechyn]

Seems to be still ongoing in upstream, @ggomaeng tried to fix it in frog as well: wevm/hono-og#37 (comment)
upstream ref: vercel/next.js#61047

[stephancill]

Update: it seems like it did not fix the problem after all. Still getting this error, just less frequently

[Tonyce]

update "@vercel/og" to "^0.6.3"

[Tonyce]

it's a OOM bug because @vercel/og, @vercel/og has release new version

[stephancill]

@Tonyce did the problem go away for you in 0.6.3?

[Tonyce]

yes, I ran a stress test and everything seemed fine.