Skip to content
Browse files

Merge pull request #7003 from philiqq/master

Fix Bleak House link in debugging guide. Closes #7002
  • Loading branch information...
2 parents 3bbc2fb + 266ccc3 commit 367b0c6e5e0ace0cb556357793264b8f80143ac2 @carlosantoniodasilva carlosantoniodasilva committed Jul 8, 2012
Showing with 2 additions and 2 deletions.
  1. +2 −2 guides/source/debugging_rails_applications.textile
View
4 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

0 comments on commit 367b0c6

Please sign in to comment.
Something went wrong with that request. Please try again.