Memory leak after upgrade Rails 5.2 to 6.0.0

Question

Has anyone experienced this? We upgraded a project from Rails 5.2 to Rails 6.0.0 and after this, the memory consumption skyrocketed... In the release candidate environment, it works fine, but in production, the container dies because of the memory usage... The instances we have in 5.2 can do just fine with 1GB RAM, but the instances we test for Rails 6.0.0 dies immediately, even if we give them 4GB ram.

We already tested https://github.com/schneems/derailed_benchmarks, but the require gems just increased like 10 MiB in total.

We have some heavy queries but we don't know why this happens in Rails 6 and not in Rails 5.

Happened to us as well, had to rollback it. we couldn't reproduce this locally, we are trying to figure out a way to debug this. — Yosi, Sep 13 '19 at 22:22
Yeah, same here. We just rolled back as it's hard to figure out where this is coming from. — ujh, Sep 18 '19 at 11:45
This could be related: https://github.com/rails/rails/issues/36963 — ujh, Sep 18 '19 at 11:51
@ujh in our case we include specific libraries of rails, so this can't affect us — Yosi, Sep 20 '19 at 23:14

score 1 · Answer 1 · answered Mar 01 '20 at 10:53

1

This hugely depends on what gems you have. Also, I would start by making use of a monitoring tool like Scout or NewRelic to understand where/how is the leak happening.

answered Mar 01 '20 at 10:53

Alan Joseph

89
5

Mahipal · Answer 2 · 2023-06-08T10:33:30.937

0

I have faced the issue in rails with AWS ECS Farget (Docker).

Taken actions.

Update latest rails 6 version (6.1.7.3)
Allow all ip and my domain in production.rb file. check

Now its working perfect.

edited Jun 08 '23 at 10:33

answered Jun 08 '23 at 10:32

Mahipal

1
3

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jun 15 '23 at 08:35

Memory leak after upgrade Rails 5.2 to 6.0.0

2 Answers2