diff options
| author | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2012-07-08 09:55:16 -0700 |
|---|---|---|
| committer | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2012-07-08 09:55:16 -0700 |
| commit | 367b0c6e5e0ace0cb556357793264b8f80143ac2 (patch) | |
| tree | b756cc4a000375d6225df2607b01ae61ae35c166 /guides/source | |
| parent | 3bbc2fb9943c3f9ddb64c787ace4dda63e9a69cb (diff) | |
| parent | 266ccc3d341c91240a1f9f8b87953b8ba6a107d6 (diff) | |
| download | rails-367b0c6e5e0ace0cb556357793264b8f80143ac2.tar.gz rails-367b0c6e5e0ace0cb556357793264b8f80143ac2.tar.bz2 rails-367b0c6e5e0ace0cb556357793264b8f80143ac2.zip | |
Merge pull request #7003 from philiqq/master
Fix Bleak House link in debugging guide. Closes #7002
Diffstat (limited to 'guides/source')
| -rw-r--r-- | guides/source/debugging_rails_applications.textile | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/debugging_rails_applications.textile b/guides/source/debugging_rails_applications.textile index cc172042e9..b0b3e6a518 100644 --- a/guides/source/debugging_rails_applications.textile +++ b/guides/source/debugging_rails_applications.textile @@ -626,7 +626,7 @@ In this section, you will learn how to find and fix such leaks by using tools su h4. BleakHouse -"BleakHouse":https://github.com/fauna/bleak_house/tree/master is a library for finding memory leaks. +"BleakHouse":https://github.com/evan/bleak_house/ is a library for finding memory leaks. If a Ruby object does not go out of scope, the Ruby Garbage Collector won't sweep it since it is referenced somewhere. Leaks like this can grow slowly and your application will consume more and more memory, gradually affecting the overall system performance. This tool will help you find leaks on the Ruby heap. @@ -675,7 +675,7 @@ To analyze it, just run the listed command. The top 20 leakiest lines will be li This way you can find where your application is leaking memory and fix it. -If "BleakHouse":https://github.com/fauna/bleak_house/tree/master doesn't report any heap growth but you still have memory growth, you might have a broken C extension, or real leak in the interpreter. In that case, try using Valgrind to investigate further. +If "BleakHouse":https://github.com/evan/bleak_house/ doesn't report any heap growth but you still have memory growth, you might have a broken C extension, or real leak in the interpreter. In that case, try using Valgrind to investigate further. h4. Valgrind |