Skip to content
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

Fix possible memory leak? #132

Open
cbeer opened this issue Sep 19, 2023 · 0 comments
Open

Fix possible memory leak? #132

cbeer opened this issue Sep 19, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@cbeer
Copy link
Member

cbeer commented Sep 19, 2023

$ docker logs folio-graphql
🚀 Server ready at http://localhost:4000

<--- Last few GCs --->

[1:0x7fea2b452510] 78138632 ms: Mark-Compact 4040.2 (4143.3) -> 4038.5 (4143.8) MB, 2051.45 / 0.01 ms  (average mu = 0.128, current mu = 0.003) allocation failure; scavenge might not succeed
[1:0x7fea2b452510] 78142580 ms: Mark-Compact 4039.8 (4144.1) -> 4039.0 (4144.0) MB, 3945.12 / 0.01 ms  (average mu = 0.055, current mu = 0.001) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
@cbeer cbeer moved this from 📋 Backlog to 🔖 Ready in Searchworks/FOLIO Summer 2022/23 Sep 19, 2023
@cbeer cbeer added the bug Something isn't working label Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🔖 Ready
Development

No branches or pull requests

1 participant