Geek Answers Handbook

A new relic causing a memory leak / bloat?

I tore my hair, trying to determine the reason for the memory that my application uses, is constantly growing, to such an extent that during production on the hero it fails and falls.

After quite extensive research, using Top to watch RSIZE growing locally, and using Oink to try to pinpoint, I just couldn't find what was wrong.

Then I found a post here that is mentioned in one of the comments on the New Relic stone causing the same problem. As a test in development, I commented on the gem, and now without it its memory usage seems pretty stable at around 100 million, while with the gem installed it grows to such an extent that I can increase it to almost 1 GB! Obviously, this behavior is the root of the application going down to Heroku.

Has anyone else had this with New Relic? I would like to continue to use it, I think this is a great service, but I can not, if this is the root of this memory leak. Any suggestions on how I can fix this?

I am running Rails 3.2.0 and Ruby 1.9.2

When I run the Gem List, it shows that I have newrelic_rpm (3.6.0.83, 3.5.6.46, 3.5.5.38, 3.4.2.1, 3.4.2)

My Gemfile just references the gem 'newrelic_rpm', so should I specify a version?

+6
source share
1 answer

It seems that this may be allowed, but if you continue to see the use of a huge resource for the New Relic Ruby agent, you should definitely contact Support immediately. I have not seen anything like this for a Ruby agent, so I would definitely be interested to see. https://support.newrelic.com/home

+2
source

More articles:


All Articles