-
Notifications
You must be signed in to change notification settings - Fork 483
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
[Bug]: New library scan crashes server #2750
Comments
What are the file formats of the ebooks you are scanning in? If you check the scan log is there a place where it stops that we can see? |
These are the logs from the container:
That last part keeps repeating until I kill the process |
also, regarding the file formats:
The Is any of these formats known to cause issues? |
I think the |
yup that fixes it. both cbr and cbz seem to be causing issues. one thing to note though, they do seem to be getting partially processed. If i start a scan with a cbr/cbz file present, it goes into the wasm error loop. if i then move the files out of the directory, this shows up in the logs:
So they do seem to be somewhat processed. I do not know much about this project so no clue why this is 😅 |
this seems unfeasible for moderately big libraries. are all book files buffered in memory at once?? 😬 also, does this happen with audiobooks too? or just cbz? |
It's only with some cbz/cbr and ebook files. |
i have the same problem. i just created a new Library and added about 40 cbz files. the first 20 where scanned but it took ages. after that it just crashes the server. |
Tested adding comics for the first time and ran into this issue. System froze then crashed. Tried creating a small <1GB library and that completed, but noticed memory wasn't released on completion of successful scan. ABS required restart to resolve. I also see the below error, both when memory completely fills and crashes and when scaning a small library so no crash, but memory is not released: 'wasm streaming compile failed: TypeError: Failed to parse URL from /client/dist/libarchive/wasm-gen/libarchive.wasm' EDIT - I subsequently also tried adding a couple of issues at a time after successfully scanning in and restarting the ABS container to release memory, but after a couple of times, hit the ceiling where it would crash again. So files already scanned into library also contribute to the memory usage issue on new scan. Which means cannot add to library incrementally either. |
Unfortunately fixing of error #2856 doesn't resolve this issue. It possibly is stopping the application from crashing, but just makes my entire Synology grind to a halt indefinitely |
Still running into this issue as well. I've tried removing new entries to back-track if there might be a corrupt cbz file causing it, but haven't pinpointed a specific file for it yet. |
I also have this issue with .cbr files. I've noticed that 64/75 of Docker logs:
|
Hi, i've the same issue. I'm on a raspberry pi with 4Gb of RAM. And i can't add my CBZ files. I'm on the Error : wasm streaming compile failed: TypeError: Failed to parse URL from /client/dist/libarchive/wasm-gen/libarchive.wasm' I've also try to limit my container with : deploy:
resources:
limits:
cpus: "1.0"
memory: "512M"
reservations:
cpus: "0.5"
memory: "256M" Still get the error .... 😒 |
I'm also having the same issues with cbr files:
Init v2.12.1 |
It looks like the issue is in libarchive.js preventing it from automatically closing the archive once it has been opened adding archive.close() wherever we have Archive.open() just before returning would prevent having everything in memory all at the same time. at the very least parseComicMetadata.js parse function and extractCoverImage. it probably also needs to be added wherever the comic reader is extracting files but I have not really looked into that. |
Thanks for helping track that down. I attempted a fix here #3312 for the server crashing during a scan if you want to help test it (I don't actually have any comic files and am testing with homemade CBR/CBZ). |
Is this still an issue? |
works for me 👍 another issue now that I can read it is that i can't zoom out to see all of it, but I have to scroll a lot |
Describe the issue
This is on a fresh install of audiobookshelf.
I added a new library for ebooks. I pointed the folder to my calibre data location and started the first scan. This maxes out the ram and eventually the server becomes unresponsive and I have to reboot the VM.
At first I tried with 4GB of RAM, and it crashed. I gave it 8GB and it crashed again. This is with around ~150 ebooks, so nothing big (5.4GB in total).
I have seen similar issues where the culprit is ffprobe spawning without limit, but it seems it is not the case here. All the ram is taken up by the node process, only 1/2 instances of ffprobe are running.
Steps to reproduce the issue
Audiobookshelf version
v2.8.0
How are you running audiobookshelf?
Docker
The text was updated successfully, but these errors were encountered: