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

Investigate benchmarking memory leaks #514

Open
hmdhk opened this issue Dec 4, 2019 · 1 comment
Open

Investigate benchmarking memory leaks #514

hmdhk opened this issue Dec 4, 2019 · 1 comment
Labels
benchmarks

Comments

@hmdhk
Copy link
Contributor

hmdhk commented Dec 4, 2019

Following our efforts for benchmarking in #26, we need to capture any memory leaks.
@hmdhk hmdhk mentioned this issue Dec 4, 2019
Closed
12 tasks
@hmdhk
Copy link
Contributor Author

hmdhk commented Dec 6, 2019

We can investigate using await client.send('HeapProfiler.collectGarbage') to force garbage collection before and after sending (multiple transactions) and compare the memory residue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
benchmarks
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hmdhk