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

Investigate possible memory leaks (part 1) #54

Merged
merged 63 commits into from
Oct 19, 2023

Conversation

LSViana
Copy link
Collaborator

@LSViana LSViana commented Oct 15, 2023

Partially closes #34.

…ose() to force memory clean-up since GC takes too long to kick-in
@LSViana LSViana self-assigned this Oct 15, 2023
@LSViana LSViana linked an issue Oct 15, 2023 that may be closed by this pull request
82 tasks
@LSViana LSViana force-pushed the 34-investigate-possible-memory-leaks branch 2 times, most recently from f08401b to 931dcbe Compare October 16, 2023 01:59
@LSViana LSViana force-pushed the 34-investigate-possible-memory-leaks branch from 931dcbe to 4b0d29d Compare October 16, 2023 02:00
@LSViana LSViana changed the title Investigate possible memory leaks Investigate possible memory leaks (part 1) Oct 19, 2023
@LSViana LSViana merged commit a3053da into main Oct 19, 2023
4 checks passed
@LSViana LSViana deleted the 34-investigate-possible-memory-leaks branch October 19, 2023 10:58
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

Successfully merging this pull request may close these issues.

Investigate possible memory leaks
1 participant