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 memory leaks #1620

Open
klntsky opened this issue May 21, 2024 · 0 comments
Open

Investigate memory leaks #1620

klntsky opened this issue May 21, 2024 · 0 comments
Labels
needs investigation

Comments

@klntsky
Copy link
Member

klntsky commented May 21, 2024

There are rumors that despite using GC, we still have memory leaks somewhere (based on observations related to a client's project).

I have a feeling that it might be applyArgs.

We need to adapt this code to be able to test arbitrary Contract scenarios and see if any of the tests trigger the leak.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@klntsky