On Oct 1, 2007, at 5:54 AM, Aleksey Kondratenko wrote:
> > About a month ago I've found similar (or, probably, same) leak while > checking our application for leaks. It leaks very slow. And it's seems > to be not Rails issue. Something with $1, $2, ... variable handling in > ruby itself. I think I still have those valgrind report files at home. > > I had not enough time to dig it seriously deep and code in that > place of > MRI is not very easy, so I gave up. that is good to know. everyone who has reported so far has seen the same results: a very slow leak over time. of course it only shows up with sessions, but that is going to affect just about every rails project. at this point i'm more concerned with finding a workaround in rails than trying to patch ruby - but i'm not sure if it's possible. i'm running out of steam too. nevertheless this is a pretty steady leak - it should be fixable. cheers. a @ http://drawohara.com/ -- we can deny everything, except that we have the possibility of being better. simply reflect on that. h.h. the 14th dalai lama --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
