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

Cannot detect memory leaks with new garbage collector #343

Open
jtenner opened this issue Apr 28, 2021 · 0 comments
Open

Cannot detect memory leaks with new garbage collector #343

jtenner opened this issue Apr 28, 2021 · 0 comments
Assignees
Labels
Breaking Change 💥 An API Is Going to Change Bug 🐛 Something isn't working

Comments

@jtenner
Copy link
Contributor

jtenner commented Apr 28, 2021

@willemneal looking at this RTrace output, I can very clearly see that the references sometimes don't properly get collected.

[Success]: ✔ float to int maps
 [Success]: ✔ different sized float to float maps
 [Success]: ✔ object to int maps RTrace: +32
 [Success]: ✔ float to string maps, with emoji RTrace: -25
 [Success]: ✔ negative float to string maps
 [Success]: ✔ int to empty string maps RTrace: -4
 [Success]: ✔ int to complex object maps RTrace: +36
 [Success]: ✔ int to complex object maps, with multiple and circular references RTrace: +2
 [Success]: ✔ int to nullable object maps RTrace: -21
 [Success]: ✔ infinite floats to float maps RTrace: -24

Calling the garbage collector after every test might be worth while.

Thoughts?

@jtenner jtenner added Bug 🐛 Something isn't working Breaking Change 💥 An API Is Going to Change labels Apr 28, 2021
@jtenner jtenner self-assigned this Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change 💥 An API Is Going to Change Bug 🐛 Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant