-
Notifications
You must be signed in to change notification settings - Fork 943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with offthreadvideo extracting frames on lambda with preflight request differences. #3865
Comments
In my situation, sometimes the video gets generated but sometimes it doesn't. My guess is the RAM usage. IDK if this helps but these are my below configs - Bundle: https://remotionlambda-d5o59m07tl.s3.ap-southeast-1.amazonaws.com/sites/video-staging/index.html InputProps example (let me know if you need more):
|
Please note that we didn't face this situation in lambda, but it happens in a ubuntu pm2 server, we are trying to have an instance of g4dn.xlarge, with 6GB ram within the pm2 (reserving the remaining RAM for basic operations like |
Also attaching our error log and out log in case it is helpful out-log link (too large so I put on google drive): https://drive.google.com/file/d/1Q-FJI5S27ug6NcK7kATZbMJ6qs3zEfQk/view?usp=sharing |
We'll still investigate the issue until the end, but I am closing the issue because OffthreadVideo doesn't have the problem as described in the title. OffthreadVideo does reply to preflight requests correctly (if there are any) and immediately. This issue is just the same as https://remotion-git-delay-render-proxy-docs-remotion.vercel.app/docs/troubleshooting/delay-render-proxy |
From message posted on Discord by jonnyburger
hmm, thanks for posting!
that seems problematic actually, something that might have gone under my radar and might have just surfaced it
offthreadvideo should not try to extract frames when there is a preflight request
normally there is no preflight request except when the domains differ
but I just realized that on lambda this is different
the website is hosted on S3 but the asset is proxied through localhost
I'll file that! currently I am a bit slower because I am going to react conf but I'm trying to get it this fixed in a new update soon
did you delete the original message? I cannot read it anymore 🤔
The text was updated successfully, but these errors were encountered: