-
Notifications
You must be signed in to change notification settings - Fork 4
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
Clicking "Watch in Browser - MP4" works w/ 8GB RAM but crashes calibre-web.service w/ 2GB RAM / memory (MP4 is 1.0GB; users see "502 Bad Gateway" due to OOM crash) #79
Comments
Tangentially-related diagnostics — to inform very purposefully tight codec/compression choices (PR #63 etc) alongside:
|
RECAP:
calibre-web/scripts/lb-wrapper Lines 10 to 14 in 5758715
|
Does the 9-hour video (8:54:03) below (https://youtu.be/9M4XKi25I2M) fail in the same way? |
@deldesir is the failure to download @nzola's 2h video https://youtu.be/Zm-ROp6EMZo ("PARLONS EN LES SONDAGES EN RDC") related? |
@mabuelhagag will take a look at this issue over coming days/weeks — ideally towards streaming 32 videos[*] simultaneously to 32 student devices, using IIAB on a 1GB RAM Raspberry Pi — as this used to work well in 2016 (FYI our testing 8+ years ago used KA Lite / Khan Academy Lite). Thank you Mohamad! [*] No matter the duration of each video, e.g. 9-minute videos or 9-hour videos. 🙏 NOTE: Some of those tests 8+ years ago weren't perfect, as we initially tested streaming of the very same video to all 32 (WiFi-connected) student devices. But more complete testing later confirmed that we could indeed stream DIFFERENT videos streamed (simultaneously) to the 32 student devices. ✅ |
1h41m video (https://youtu.be/vbXu7WaifAo) is downloadable to IIAB even on VM's with 1.5GB RAM or less, and thumbnail/cover/poster seems to appear properly every time. However:
calibre-web.service
to crash, on regular VM's with 2GB or less.Service crashing needs to be solved not just mitigated.
Hiding the problem is not a healthy option in my opinion — e.g. at this time I'm personally not in favor of partial solutions like these 2 proposed workarounds:
Basic diagnostics below, towards getting us on the road to a proper fix:
Related:
The text was updated successfully, but these errors were encountered: