Skip to content
This repository
Browse code

fix broken bleak_house link

  • Loading branch information...
commit 266ccc3d341c91240a1f9f8b87953b8ba6a107d6 1 parent 7404cda
Philipp Franke authored July 08, 2012 philippfranke committed July 08, 2012
4  guides/source/debugging_rails_applications.textile
Source Rendered
@@ -626,7 +626,7 @@ In this section, you will learn how to find and fix such leaks by using tools su
626 626
 
627 627
 h4. BleakHouse
628 628
 
629  
-"BleakHouse":https://github.com/fauna/bleak_house/tree/master is a library for finding memory leaks.
  629
+"BleakHouse":https://github.com/evan/bleak_house/ is a library for finding memory leaks.
630 630
 
631 631
 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.
632 632
 
@@ -675,7 +675,7 @@ To analyze it, just run the listed command. The top 20 leakiest lines will be li
675 675
 
676 676
 This way you can find where your application is leaking memory and fix it.
677 677
 
678  
-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.
  678
+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.
679 679
 
680 680
 h4. Valgrind
681 681
 

0 notes on commit 266ccc3

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