http://joeshaw.org/2006/03/17/386 Wed, 18 Mar 2009 16:01:50 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://joeshaw.org/2006/03/17/386/comment-page-1#comment-3499 Beagle Newsletter » Blog Archive » Beagle Newsletter - 3 April 2006 Wed, 28 Jun 2006 15:44:42 +0000 http://joeshaw.org/?p=386#comment-3499 [...] It is no secret that in the past Beagle has, on occasion, consumed far to much system memory when run for a long period of time. As this was certainly a large annoyance and deterred people from using Beagle, it has received a lot of attention as of late. Joe Shaw, utilizing the mono memory profiling tool Heap-Buddy, was able to track down several key issues in Beagle and Mono that have been taken care of as of the 0.2.3 release. Other improvements in this area have occured recently in CVS. Read all about it on Joe’s Blog: http://joeshaw.org/2006/03/17/386 [...] [...] It is no secret that in the past Beagle has, on occasion, consumed far to much system memory when run for a long period of time. As this was certainly a large annoyance and deterred people from using Beagle, it has received a lot of attention as of late. Joe Shaw, utilizing the mono memory profiling tool Heap-Buddy, was able to track down several key issues in Beagle and Mono that have been taken care of as of the 0.2.3 release. Other improvements in this area have occured recently in CVS. Read all about it on Joe’s Blog: http://joeshaw.org/2006/03/17/386 [...]

]]> http://joeshaw.org/2006/03/17/386/comment-page-1#comment-1108 joe shaw Sat, 29 Apr 2006 17:25:47 +0000 http://joeshaw.org/?p=386#comment-1108 [...] Now that Mono 1.1.13.5 — which has the fix for the leak I previously blogged about — has been out for a while, I decided it was time to back out my buggy workaround and just require it. It’s ironic that the workaround, when it failed, would cause Beagle to try to allocate huge swaths of memory. This release also fixes some problems when the beagle-crawl-system cronjob would stop working because some versions of su are finicky about the order of their command-line arguments, and the mysterious case of why some documents wouldn’t open when clicked on in beagle-search. (Turns out, it wouldn’t launch things from shell scripts.) As I mentioned in the release announcement, Beagle wouldn’t be where it is today without the help of over 100 people who have supported and contributed to it over the past two years. I’d like to recognize those people in this undoubtedly incomplete list: [...] [...] Now that Mono 1.1.13.5 — which has the fix for the leak I previously blogged about — has been out for a while, I decided it was time to back out my buggy workaround and just require it. It’s ironic that the workaround, when it failed, would cause Beagle to try to allocate huge swaths of memory. This release also fixes some problems when the beagle-crawl-system cronjob would stop working because some versions of su are finicky about the order of their command-line arguments, and the mysterious case of why some documents wouldn’t open when clicked on in beagle-search. (Turns out, it wouldn’t launch things from shell scripts.) As I mentioned in the release announcement, Beagle wouldn’t be where it is today without the help of over 100 people who have supported and contributed to it over the past two years. I’d like to recognize those people in this undoubtedly incomplete list: [...]

]]> http://joeshaw.org/2006/03/17/386/comment-page-1#comment-680 First take on profiling Muine Sun, 19 Mar 2006 12:55:06 +0000 http://joeshaw.org/?p=386#comment-680 [...] Posted by Brandon Hale Sun, 19 Mar 2006 12:23:00 GMT After reading about Joe’s handywork patching a beagle leak, I watched beagled in top, sorted by RSS. I was surpised to see that Muine had a significantly higher RSS than beagled, or even Firefox. [...] [...] Posted by Brandon Hale Sun, 19 Mar 2006 12:23:00 GMT After reading about Joe’s handywork patching a beagle leak, I watched beagled in top, sorted by RSS. I was surpised to see that Muine had a significantly higher RSS than beagled, or even Firefox. [...]

]]>