Running horizon:watch runs multiple instances instead of killing the old one #19
Replies: 2 comments
-
I does work on my configuration (got a Mac here). Feel free to submit a PR that makes this work in your environment. |
Beta Was this translation helpful? Give feedback.
-
I've had this running in the background while doing different tasks (programming, graphics, etc.). And suddenly everything froze. I managed to open up a terminal to find out that 334 horizon processes were eating up ~48 GB RAM and using up 12 Cores. I'm using Linux and have horizon running inside a docker container using sail. This is also a problem when trying to use Xdebug (which I wasn't in the above case). PHPStorm allows for a maximum of 10 simultaneous debugger connections. Because the old horizon processes aren't terminated those connections are all blocked pretty quickly causing the whole app to freeze. @freekmurze if you need any more info, please lmk |
Beta Was this translation helpful? Give feedback.
-
I absolutely love the idea of this package. When I run it though, executing one job will end up running it multiple times and my machine's processes get filled up with php instances.
My processes:
All of those processes go away after I end horizon:watch
As far as I know everything is pretty stock for both laravel and for this package, I didn't modify anything.
Beta Was this translation helpful? Give feedback.
All reactions