Links to issues, pull requests or articles demonstrating known memory leaks (gems are listed alphabetically).
Leaky Gems alternatives and similar gems
Based on the "Debugging Tools" category.
Alternatively, view Leaky Gems alternatives based on common mentions on social networks and blogs.
Byebug8.5 0.0 L4 Leaky Gems VS ByebugDebugging in Ruby 2
did_you_mean7.4 0.0 L5 Leaky Gems VS did_you_meanThe gem that has been saving people from typos since 2014
Pry Byebug7.4 7.5 L5 Leaky Gems VS Pry ByebugStep-by-step debugging and stack navigation in Pry
Rails Footnotes6.8 0.0 L5 Leaky Gems VS Rails FootnotesEvery Rails page has footnotes that gives information about your application and links back to your editor
Seeing Is Believing6.2 0.0 L2 Leaky Gems VS Seeing Is BelievingDisplays the results of every line of code in your file
Xray6.2 1.6 L5 Leaky Gems VS Xray☠️ A development tool that reveals your UI's bones
ruby_jard5.3 0.0 Leaky Gems VS ruby_jardJust Another Ruby Debugger. Provide a rich Terminal UI that visualizes everything your need, navigates your program with pleasure, stops at matter places only, reduces manual and mental efforts. You can now focus on real debugging.
debase2.9 0.0 L4 Leaky Gems VS debaseA fast implementation of the standard debugger debug.rb for Ruby 2.0.0
FlowTrace0.6 0.0 Leaky Gems VS FlowTraceBrand new remote app inspecting tool. Declare feature steps and receive params, stack trace and whatever you want.
Rbcat0.1 4.6 Leaky Gems VS RbcatRbcat it's a CLI tool which reads content from standard input and colorizes it by set of regex rules
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Leaky Gems or a related project?
A list of gems that have memory leaks
Links to issues, pull requests or articles demonstrating known memory leaks (gems are listed alphabetically):
- celluloid > 0.16.0, < 0.17.2
- csspool < 4.0.3
- grape < 0.2.5
- oj < 2.12.4
- redcarpet < 3.3.3
- redis = 3.3.0
- sidekiq < 3.5.1
- therubyracer < 0.12.2
- zipruby <= 0.3.6
Your Ruby app leaks memory if you see gems above in your Gemfile.lock. The list above may save you a week or more of your personal life.
A list of gems that have memory issues (but not actual leaks)
It appears some contributors submit gems with known memory issues, but not actual leaks. While those issues don't qualify as leaks they may still be important. I prefer listing them here to help other developers rather than just hiding them.
Links to known memory issues (gems are listed alphabetically):
- delayed_job >= 4.06
- libxml-ruby < 2.9.0 with Nokogiri RC3
- newrelic_rpm >= 3.9.4, <= 3.9.7
- sequel >= 2.12.0
- stomp <= 1.3.5
Feel free to submit a PR if you find any memory leaks in gems. The format is the following:
[leaky gem name and versions affected](link to confirm)
- Graham Conzett @conzett
- Jacob Oakes @oakesja
- Juan Ignacio Sánchez Lara @juanignaciosl
- Ilya Vassilevsky @vassilevsky
- Sebastiaan Pouyet @srpouyet
- Michal Kulesza @mic-kul
- Benoit Tigeot @benoittgt
- Jolyon Pawlyn @jpawlyn
- Shai Coleman @shaicoleman
- Ryan Rosenblum @rrosenblum
- Lumir Olivares @lumir
After almost 4 years from the initial request a gem that checks
Gemfile.lock for leaky gems has been created – https://github.com/rubymem/bundler-leak.