-
-
Notifications
You must be signed in to change notification settings - Fork 200
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 in v8go.(*Value).String #367
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Calling String() on
info.Args()
in callback causes[email protected]
to leak memory.pprof output:
Call graph:
We have 12 nodes each running a pool of 128 isolates.
The service uses v8go to process events at a rate of ~ 40 req/s per node.
We are reliably closing contexts after every event.
We are reliably disposing of each isolate after it processes ~100 events or when its heap exceeds 20MB.
We call
runtime.GC()
manually after every isolate disposal.The new
GOMEMLIMIT
parameter has no effect on memory growth.Memory growth remains unbounded, leading nodes to be OOMKilled by Kubernetes.
Downgrading to
[email protected]
does not solve the issue.Has anyone else experienced this behavior before?
The text was updated successfully, but these errors were encountered: