You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2022. It is now read-only.
Some system information: this daemon is running on Mac OS X, using PHP 5.5 installed via homebrew. The current stable in homebrew is 5.5.23.
My daemon launches several tasks to download files from a remote host. I have a condition that occurs when, after whatever the first task is that finishes, the main runloop stops executing (or, at the very least, execute() isn't being called). All of the tasks eventually finish and I can still call log() on the parent, and if I look at a process list the daemon is still "running", but not actually doing anything and no new tasks are created.
Downgrading to PHP 5.5.20 fixes it.
I know this is a frustratingly vague bug report, so if there's anything else I can help you with I would be glad to provide assistance.
The text was updated successfully, but these errors were encountered:
rebeccathedev
changed the title
Run loops stops executing in PHP 5.5.23 after task completes.
Run loop stops executing in PHP 5.5.23 after task completes.
Apr 5, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some system information: this daemon is running on Mac OS X, using PHP 5.5 installed via homebrew. The current stable in homebrew is 5.5.23.
My daemon launches several tasks to download files from a remote host. I have a condition that occurs when, after whatever the first task is that finishes, the main runloop stops executing (or, at the very least, execute() isn't being called). All of the tasks eventually finish and I can still call log() on the parent, and if I look at a process list the daemon is still "running", but not actually doing anything and no new tasks are created.
Downgrading to PHP 5.5.20 fixes it.
I know this is a frustratingly vague bug report, so if there's anything else I can help you with I would be glad to provide assistance.
The text was updated successfully, but these errors were encountered: