Method of checking?

[anhtrantuan]

Could you demonstrate or at least brief how did you test if those gems are memory leaky?

[sergey-alekseev]

@anhtrantuan I found them during reading articles about memory leaks and debugging my application.

[emilsoman]

All of these gems are widely used so it's a bit alarming to hear that there are memory leaks in those! Not all memory growths are leaks , and sometimes even a simple GC invocation can claim a lot of allocated heap pages. It would be great if you can show that they actually leak by writing some demo scripts. Also, it may help you accept PRs more easily because you can verify by running the demo script when someone sends in a PR saying gem foo leaks.

[douglascamata]

@emilsoman most of the leaky gems in this repository have a reference to a PR or an issue in the gem's repository that describes and/or fixes the leaks. Most of them are also merged already. So they are trustable.

[posgarou]

I think the current level of proof is sufficient, especially since there's space for issues, PRs, etc. if readers disagree.