When is the memory of a (no longer used) ViewComponent released?

[dannyvanhoof]

We started using ViewComponents in combination with Motion to render orders in our application. We now somehow have the feeling (by diving into it with get_process_mem and rack_mini_profiler) that the memory allocated by these components is not released when the page is closed, so that our Rails application keeps on growing for days, to eventually be thrown out by Heroku.

Question: is this indeed the case? And if yes: what can we do to reclaim the memory used?

[BlakeWilliams]

I would have thought that view component instances would be garbage collected like any other object. 🤔

@dannyvanhoof Is there any way you could share your findings, or even better, a minimal reproduction of the issue we can dive into?

[dannyvanhoof]

@BlakeWilliams If you're convinced that this should be garbage collected, then it's probably related to Motion keeping the ViewComponent alive, just in case an event might pop up...
Let me first check with the Motion guys, whether this does ring a bell for them...

[BlakeWilliams]

Sounds good. I'm not familiar with Motion, do you mean https://github.com/unabridged/motion?

[dannyvanhoof]

Indeed

[BlakeWilliams]

It looks like this issue is related to the motion library, the solution is being tracked here: unabridged/motion#49