I'll bring this up at tonight's Seattle Ruby Hacking Night--I suspect that someone there knows the internals of rubygems well enough to help fix the problem.
Scott On 8/7/06, Steve Longdo <[EMAIL PROTECTED]> wrote: > I posted a follow up showing some more specfic memory hogs. I haven't been > able to get anyone involved with RubyGems to clue me into why it needs so > much memory, yet. Anyone that reads this and can provide me some insight as > the runtime shenanigans of RubyGems please do leave a comment on my site or > feel free to send me an email directly mocking me :-) > > The post: > http://www.stevelongdo.com/articles/2006/08/08/rubygems-dependency-management-and-memory-use > > -- > > Thanks, > -Steve > http://www.stevelongdo.com > > > On 8/7/06, Scott Laird <[EMAIL PROTECTED]> wrote: > > Thanks. Memory leak debugging with Rails is difficult. > > Unfortunately, slower leaks are even harder to find and harder to > > verify as fixed, but we'll find it and fix it. > > > > > > Scott > > > > On 8/7/06, Steve Longdo < [EMAIL PROTECTED]> wrote: > > > I've done a quick write up about this on my blog. I've also been doing > some > > > preliminary memory profiling. I'll be writing more about that soon. > > > > > > > http://www.stevelongdo.com/articles/2006/08/04/typo-4-0-and-memory-reduction > > > > > > > > > -- > > > Thanks, > > > -Steve > > > http://www.stevelongdo.com > > > > > > > > _______________________________________________ > Typo-list mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/typo-list > > _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
