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.

Sign up for GitHub

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

Jump to bottom

Memory leak issue caused by incorrect node-cache configuration #63

Closed
wukko opened this issue Dec 17, 2022 · 2 comments
Closed

Memory leak issue caused by incorrect node-cache configuration #63

wukko opened this issue Dec 17, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@wukko
Copy link
Member

wukko commented Dec 17, 2022

no idea if this is caused by cobalt itself or my nginx configuration, but after a few days way more ram is used by the server that cobalt is hosted on. i'll have a look into this issue in a few days (if ram usage ramps up again). if you host your own instance, you can help by checking if this issue applies to you too.

image
@wukko wukko added the bug Something isn't working label Dec 17, 2022
@lurkook
Copy link

lurkook commented Dec 21, 2022

i recommend to debug node-cache library if it really cleans expired stream metadata.

@wukko wukko changed the title Possible memory leak issue (could be related to nginx and not cobalt) Possible memory leak issue (could be related to my nginx config and not cobalt) Dec 28, 2022
@wukko wukko added the help wanted Extra attention is needed label Dec 28, 2022
@wukko wukko changed the title Possible memory leak issue (could be related to my nginx config and not cobalt) Memory leak issue caused by wrong node-cache setup Jan 13, 2023
@wukko
Copy link
Member Author

wukko commented Jan 13, 2023

@lurkook you were right, it is the node-cache library, i've fixed the issue and will publish the commit later today

https://wetdry.world/@w/109682355531091033

@wukko wukko removed the help wanted Extra attention is needed label Jan 13, 2023
@wukko wukko changed the title Memory leak issue caused by wrong node-cache setup Memory leak issue caused by incorrect node-cache configuration Jan 13, 2023
@wukko wukko closed this as completed in 3b5bf51 Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wukko @lurkook