frames-devs

Is anyone else seeing memory leak issues with frames.js and/or the Satori/Vercel OG stack? We're still digging in but this server instance only has 3 frames running on it so I imagine it has to be something with the image creation process...

haven't seen this - node will garbage collect based on max-old-space-size, it may just be a wrong value of that and not a memory leak. How are you deploying?

🎩 builder @setter /setter FID 3707 | powering digital economies | omni 🟦 🟪 🟨 ⭐️

haven't seen this - node will garbage collect based on max-old-space-size, it may just be a wrong value of that and not a memory leak. How are you deploying?
https://github.com/vercel/next.js/discussions/35526

https://stackoverflow.com/questions/48387040/how-do-i-determine-the-correct-max-old-space-size-for-node-js

OK, I think we've resolved the issue, we were using an older version of node due to this noted issue in the repo, but we were able to test & re-deploy with a later node version (v21.6.2) which doesn't appear to have the same memory leak issue:

Building FOSS via @frames, /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

OK, I think we've resolved the issue, we were using an older version of node due to this noted issue in the repo, but we were able to test & re-deploy with a later node version (v21.6.2) which doesn't appear to have the same memory leak issue:

https://github.com/framesjs/frames.js/issues/25