We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Audiobookshelf installation crashes due to out of memory limitations
NA
v2.17.6
Docker
Linux
Firefox
<--- Last few GCs ---> [7:0x7f78a1485660] 6308217 ms: Scavenge 4041.5 (4123.3) -> 4041.1 (4134.0) MB, 9.92 / 0.00 ms (average mu = 0.590, current mu = 0.207) allocation failure; [7:0x7f78a1485660] 6308266 ms: Scavenge 4047.8 (4134.0) -> 4047.1 (4134.8) MB, 9.46 / 0.00 ms (average mu = 0.590, current mu = 0.207) allocation failure; [7:0x7f78a1485660] 6308291 ms: Scavenge 4048.8 (4134.8) -> 4047.7 (4155.8) MB, 15.33 / 0.00 ms (average mu = 0.590, current mu = 0.207) allocation failure; <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
No response
The text was updated successfully, but these errors were encountered:
Does the library only have audiobooks? So not ebook files? How many files are in the library? Do you have any logs from before the crash?
You can increase the amount of memory for the node process using the steps here: #3338 (comment)
Sorry, something went wrong.
Hi, @nichwall Thanks
There are only audiobooks in the library approx 70K.
There were nothing else in the logs other than what I posted.
I increased the memory size to 8GB and is working properly at present.
No branches or pull requests
What happened?
Audiobookshelf installation crashes due to out of memory limitations
What did you expect to happen?
NA
Steps to reproduce the issue
Audiobookshelf version
v2.17.6
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Firefox
Logs
Additional Notes
No response
The text was updated successfully, but these errors were encountered: