finite_machine: Potential memory leak in v0.11.x
It appears there’s a memory leak in the v0.11 series of the gem. When we bumped to it in our app, we started to experience severe memory issues in production.
I don’t have time at the moment to do a deeper dive, but I wanted to make you aware of the issue in case you might have an inkling off the top of your head about where the problem might be. For the time being, we’ve had to revert back to v0.10.x until we can get to the bottom of it.
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 20 (18 by maintainers)
Commits related to this issue
- Fix memory leak reported by issue #42 — committed to piotrmurach/finite_machine by piotrmurach 8 years ago
- Change to remove ability to call transitions in async mode in ref to issue #42 — committed to piotrmurach/finite_machine by piotrmurach 6 years ago
Nope, we don’t use the async behavior, which makes this especially frustrating. I think you’re right that that aspect of the codebase needs another look since it seems to be the primary source of the bugs we keep running into. It’d be nice if the async feature could be layered on while being minimally invasive to the core logic of the gem. The additional complexity really seems to be an issue at the moment. 😕