Skip to content

memory leak #106

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

Closed
cike111 opened this issue Jun 19, 2024 · 0 comments
Closed

memory leak #106

cike111 opened this issue Jun 19, 2024 · 0 comments

Comments

@cike111
Copy link

cike111 commented Jun 19, 2024

          @rainyl  Your approach seems to have some effect, but it hasn't completely solved the problem.

image

Originally posted by @cike111 in #102 (comment)

@cike111 cike111 changed the title @rainyl Your approach seems to have some effect, but it hasn't completely solved the problem. memory leak Jun 19, 2024
@cike111 cike111 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 19, 2024
@cike111 cike111 reopened this Jun 19, 2024
@rainyl rainyl closed this as completed Jun 20, 2024
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

2 participants