TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Updated to add Derailed link

Browse Source
This commit is contained in:
Jesse Waites 2019-08-07 16:46:06 -04:00 committed by GitHub
parent d580d8c6dd
commit 0220b8d61f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
guides/source/debugging_rails_applications.md
View File

@ -939,7 +939,7 @@ Debugging Memory Leaks
A Ruby application (on Rails or not), can leak memory — either in the Ruby code A Ruby application (on Rails or not), can leak memory — either in the Ruby code
or at the C code level. 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. such as Valgrind.
### 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/) [Valgrind and Ruby](http://blog.evanweaver.com/articles/2008/02/05/valgrind-and-ruby/)
by Evan Weaver. 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 Plugins for Debugging
--------------------- ---------------------