Excerpts from gobigdave's message of Fri Jun 05 00:23:56 +1000 2009: > > For me, any version after 0.7.8 leaks like crazy. I'm on CentOS 5. I > have god.rb on several servers, and 0.7.8 stays right at about 20m RES > forever. Later versions jump up about 10m per day. There was a long > thread earlier about finding the leak, and it seemed to work with a > fix for 0.7.8. The leak has returned now, and the recommendation is > that it is fixed with Ruby 1.9. However, going to Ruby 1.9 is not > practical for me.
That's worth knowing. I'm using 1.9 so that's not a hurdle for me. rgh > On Jun 4, 8:19 am, Richard Heycock <[email protected]> wrote: > > Excerpts from post.john.mccarthy's message of Thu Jun 04 04:58:41 +1000 > > 2009: > > > > > > > > > Hi, I noticed that my God process steadily grows its RAM consumption. > > > God has been running on my server for about a week and it has grown to > > > 296m VIRT and 283m RES. Does anyone else see this with their God > > > process? Is there a command to restart God without affecting the > > > watches? > > > > > Thanks!, > > > John > > > > God is known to have memory leaks, it's the reason I stopped using it. > > Sorry to be so blunt but that's the way it is. > > > > rgh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "god.rb" 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/god-rb?hl=en -~----------~----~----~----~------~----~------~--~---
