After the foreman finishes, the ruby process continues to exist

[afuno]

Ruby 2.7.2, Rails 6.1.0, Foreman 0.87.2

---

I have two Rails applications. One application depends on another through an API.

I run both applications with two commands in different console windows:

foreman start -f Procfile.dev

Inside these two Procfiles:

web: bundle exec rails s -p 3000
webpacker: ./bin/webpack-dev-server

web: bundle exec rails s -p 3010
webpacker: ./bin/webpack-dev-server
worker: redis-server
worker: bundle exec sidekiq -C config/sidekiq.yml

The application terminates using the keyboard shortcut Control + C.

After that, through the monitoring app on macOS, I continue to see two ruby processes. These processes absolutely appear after the launch of Rails applications. And these processes together load the CPU at 100%.

These two processes have to be completed separately. For some reason, this command is suitable for this:

spring stop

[yangjindong]

I‘m also wondering why the spring doesn't stop automatically as expected.

[dentarg]

Maybe due to #779? That issue has been addressed in overman, a foreman fork, see #780 (comment)