Memory leak when contiune update config file which wunderctl started by up command
See original GitHub issueBug description
1: use cmd start server: wunderctl --debug true --wundergraph-dir wundergraph/examples/simple/.wundergraph 2: update wundergraph.config.json 3: use memory continue increase 4: i think this is because NewInMemory continue apply memory but not relase
How to reproduce
Expected behavior
No response
WunderGraph information
Environment & setup
- OS: mac os
- Go version: go version go1.19 darwin/arm64
- Database:
- Node.js version:
WunderCtl Version
commit: be612bb
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Memory Leak when running multiple test. Especially ... - GitHub
I'm seeing a memory leak while trying to run a basic autogenerated ... If i run jest with --runInBand , i see heap...
Read more >E1: 17: Memory Leak In VerifyandGetWorkOrder (B3100330 ...
Start "Search For Service Work Orders" (P90CD020) and Click on Add button. ... Number/Description and then click “Save and Continue” button.
Read more >How to Find, Fix, and Prevent Node.js Memory Leaks
Memory management for any application is essential. This post looks at what memory leaks are and how to avoid them in Node.js applications....
Read more >How to debug memory leaks in a Node.js application on Heroku
Having a Node.js memory leak is no fun. Learn how to debug such problems in a Node.js app on Heroku with our guide....
Read more >Running Sysmon 8.0.0? Update to 8.0.4 to Avoid a Memory ...
A memory leak exists in recent version of the Sysmon utility that could cause a computer to run out of memory and crash...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thx, could please add the pr when you fix this problem. i want to learn how to fix it
@javacode123 We were missing a call to ristretto.Cache.Close. See #401 for the whole PR. If you have any questions about it, we’re more than happy to help.