[GH-ISSUE #63] Memory leak issue caused by incorrect node-cache configuration #8872

Closed
opened 2026-04-24 14:55:47 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @wukko on GitHub (Dec 17, 2022).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/63

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

Originally created by @wukko on GitHub (Dec 17, 2022). Original GitHub issue: https://github.com/imputnet/cobalt/issues/63 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](https://user-images.githubusercontent.com/71202418/208229039-58e513b3-f006-497c-825f-8a611a34c386.png)
GiteaMirror added the bug label 2026-04-24 14:55:47 -05:00
Author
Owner

@lurkook commented on GitHub (Dec 21, 2022):

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

<!-- gh-comment-id:1360974397 --> @lurkook commented on GitHub (Dec 21, 2022): i recommend to debug node-cache library if it really cleans expired stream metadata.
Author
Owner

@wukko commented on GitHub (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

<!-- gh-comment-id:1381939094 --> @wukko commented on GitHub (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
Sign in to join this conversation.