Closed konalegi closed 1 year ago
After switching to Ruby 3.2 we started to get a memory leak. I don't have any explanation for why it so, it looks like something significant has changed in ruby 3.2 in terms of sigleton_class.eval.
sigleton_class.eval
Ruby 3.2 (without fix) (green line) vs ruby 3.0 (orange line) memory consumption graphs
after the fix has been applied
Before submitting the PR make sure the following are checked:
[Fix #issue-number]
master
After switching to Ruby 3.2 we started to get a memory leak. I don't have any explanation for why it so, it looks like something significant has changed in ruby 3.2 in terms of
sigleton_class.eval
.Ruby 3.2 (without fix) (green line) vs ruby 3.0 (orange line) memory consumption graphs
after the fix has been applied
Before submitting the PR make sure the following are checked:
[Fix #issue-number]
(if the related issue exists).master
(if not - rebase it).