Detects memory leaks in Ruby applications.
Please see the project documentation for more details.
- Getting Started - This guide explains how to use
memory-leakto detect and prevent memory leaks in your Ruby applications.
Please see the project releases for all releases.
- Disable default
increase_limit: nil.
- Introduce
free_size_minimumto monitor minimum free memory size, which can be used to trigger alerts or actions when available memory is critically low.
- Also log host memory in total memory usage logs.
- Use
process-metricsgem for accessing both private and shared memory where possible. - Better implementation of cluster
total_size_limitthat takes into account shared and private memory.
Memory::Leak::System.total_memory_sizenow considerscgroupmemory limits.
- Make both
increase_limitandmaximum_size_limitoptional (ifnil).
- Added
sample_countattribute to monitor to track number of samples taken. check!method in cluster now returns an array of leaking monitors if no block is given.Cluster#check!now invokesMonitor#sample!to ensure memory usage is updated before checking for leaks.
- Improved variable names.
- Added
maximum_size_limitto process monitor.
- Initial implementation.
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some feature'). - Push to the branch (
git push origin my-new-feature). - Create new Pull Request.
In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.