From 0220b8d61f48d2d2f59b340b770fdc8ecbc6a3cd Mon Sep 17 00:00:00 2001 From: Jesse Waites Date: Wed, 7 Aug 2019 16:46:06 -0400 Subject: [PATCH] Updated to add Derailed link --- guides/source/debugging_rails_applications.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/guides/source/debugging_rails_applications.md b/guides/source/debugging_rails_applications.md index 170c22905becf..d3bf43f2b95a9 100644 --- a/guides/source/debugging_rails_applications.md +++ b/guides/source/debugging_rails_applications.md @@ -939,7 +939,7 @@ Debugging Memory Leaks A Ruby application (on Rails or not), can leak memory — either in the Ruby code or at the C code level. -In this section, you will learn how to find and fix such leaks by using tool +In this section, you will learn how to find and fix such leaks by using tools such as Valgrind. ### Valgrind @@ -956,6 +956,10 @@ For further information on how to install Valgrind and use with Ruby, refer to [Valgrind and Ruby](http://blog.evanweaver.com/articles/2008/02/05/valgrind-and-ruby/) by Evan Weaver. +### Find a memory leak +There is an excellent article about detecting and fixing memory leaks at Derailed, [which you can read here](https://github.com/schneems/derailed_benchmarks#is-my-app-leaking-memory). + + Plugins for Debugging ---------------------