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
Ruby Arena object should use xrealloc/xfree so Ruby is aware of allocated memory #9546
Comments
We can test this theory simply by lying to it and reporting large numbers and seeing what happens |
After trying Matt's suggestion to report arbitrary large number (also adding print statement to sanity check) showed that implementing dsize (note: initial issue has typo However, Josh found this lead which seems much more promising: ffi/ffi#753 |
Looks like this worked. Will send out fix shortly. Results using the script from #9467 with local source (
|
Fixed by: #9586 |
Once the upb arena can report the number of bytes allocated (https://github.com/protocolbuffers/upb/issues/528) we should make the Ruby
Arena
object report bytes allocated via thedfree
member ofArena_type
.This will hopefully convince Ruby to run the GC more often and prevent the growing memory usage we have seen reported in #9467.
The text was updated successfully, but these errors were encountered: