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

Memory leak issue about wasm and nottinygc #1

Open
elvenlegolas opened this issue Sep 3, 2024 · 0 comments
Open

Memory leak issue about wasm and nottinygc #1

elvenlegolas opened this issue Sep 3, 2024 · 0 comments

Comments

@elvenlegolas
Copy link

elvenlegolas commented Sep 3, 2024

Hi,I've seen wasilibs/nottinygc#31 and found out that I met the exactly same problem like you did,since both proxywasm-go-sdk and nottinygc repo are archived,so there is barely no place to discuss this issue.
image
The scene we met is quite similar,we use wasm written by proxy-wasm-go sdk and built via nottinygc as envoy's plugin,and the memory leak occasionally like the pic above,the test qps is around 1000,I wonder if you have solved this issue or came up with any short-term solutions?
Any advice from you would be appreciated!
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant