-
Notifications
You must be signed in to change notification settings - Fork 495
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]: OOM When trying to download all episodes from a large podcast #3601
Comments
Related to #3338 |
Doing a search in issues that specific podcast has caused a few OOM crashes. Here is one #2075 (comment) I did a quick test and the issue is that the download queue in We can fix this by refactoring the queue so that it only stores the fields from the RSS feed that are sent in by the request, and construct the |
I also checked, and I think that is not the actual issue. I think the actual issue is emitting I believe this causes creation of O(n^2) large objects in quick succession, before they're even sent over the socket, which causes the crash. If you remove this emit call, or put it after the loop that queues all the downloads, the OOM issue is gone. |
Yep removing that it only takes up ~250MB of heap. The socket event should definitely not be sending the entire queue. |
Fixed in v2.17.0. |
What happened?
I'm opening this to capture this bug opened on audiobookshelf-windows, as I don't believe this is a Windows-specific bug.
I was able to reproduce it both on the official audiobookshelf-windows 2.16.2 as well on dev server built from latest source, on Windows 11.
What did you expect to happen?
Expecting server not to crash
Steps to reproduce the issue
Add
pageSubmit
Find Episodes
button (magnifying glass)Select all episodes
Download 2437 episodes
Server crash on OOM
Audiobookshelf version
v2.16.2
How are you running audiobookshelf?
Built from source
What OS is your Audiobookshelf server hosted from?
Windows
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
Following the server process memory usage on Task Manager, I can confirm it quickly goes up to ~4Gb before it crashes.
The text was updated successfully, but these errors were encountered: