-
Notifications
You must be signed in to change notification settings - Fork 22
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
Crashes after a few days - memory leak? #22
Comments
This error has an open issue with OpenCV.js: opencv/opencv#19397 Though I'm not convinced it isn't something I've done. Are you able to check memory usage when it first starts, maybe a day later, and finally when the error crops up? Maybe there's a memory leak somewhere. |
there's very much a memory leak, it starts at around 4g used and after a day it's around 8g I set the container to cap memory to 6.5 gigs, and this seems to restart the container once it goes over that I have two 4K cameras H265, 15 fps. I'm not sure if the memory leak is coming from FFmpeg. |
Can you post your (sanitized) config here? I'd like to try and replicate the issue. |
|
also the docker compose
|
Seeing same issue: Failed to process image: RuntimeError: memory access out of bounds |
Got this after a few days uptime, restarted the container and it did it again after a few days
Error would repeat and spam the console
The text was updated successfully, but these errors were encountered: