Scheduler emit a javascript error in production build

[SRWieZ]

What were you trying to do?

Just running a production app

What happened?

Starting the scheduler seems to time out.

How to reproduce the bug

Context (TBD):

• I got this error after waking up my Mac from sleep, I think.
• I had to close and reopen the app. otherwise, it will get back to me every minute, I believe.
• I have a subminute scheduler (every ten seconds)

Production build here: https://github.com/SRWieZ/tailscale-notifier/releases

Package Versions

{
    "installed": [
        {
            "name": "nativephp/electron",
            "direct-dependency": true,
            "homepage": "https://github.com/nativephp/electron",
            "source": "https://github.com/NativePHP/electron/tree/main",
            "version": "dev-main e733d3e",
            "description": "Electron wrapper for the NativePHP framework.",
            "abandoned": false
        },
        {
            "name": "nativephp/laravel",
            "direct-dependency": false,
            "homepage": "https://github.com/nativephp/laravel",
            "source": "https://github.com/NativePHP/laravel/tree/1.0.0-beta.4",
            "version": "1.0.0-beta.4",
            "description": "Laravel wrapper for the NativePHP framework.",
            "abandoned": false
        },
        {
            "name": "nativephp/php-bin",
            "direct-dependency": false,
            "homepage": "https://nativephp.com",
            "source": "https://github.com/NativePHP/php-bin/tree/1.0.0",
            "version": "1.0.0",
            "description": "PHP binaries used by the NativePHP framework",
            "abandoned": false
        }
    ]
}

PHP Version

8.3

Laravel Version

11

Node Version

22

Which operating systems have you seen this occur on?

No response

OS version

macOS 15.4 (24E248)

Notes

I'll do additional tests, before coming up with a fix.
If anyone has the same issue, please report to me here.

[SRWieZ]

I confirm having the alert box every minutes
and I confirm having the alert box popping up every minute until I close the app.

Nothing in the logs.

[SRWieZ]

Unfortunately I still got the error.

This error arises when the app loses connections to system resources, resulting in invalid file descriptors.

I'll continue my investigation.

[SRWieZ]

Got the same with Relay

[gwleuverink]

There have been some changes in how process.exit() is handled internally in Electron 37. I wonder if that might resolve this issue.

NativePHP/electron#233

Utility Processes will now warn with an error message when an unhandled rejection occurs instead of crashing the process.

Sadly we can't update to 37 yet, due to a conflict with another dependency: NativePHP/electron#233

[gwleuverink]

I haven't encountered this error in a while.

I did find something that might be related to this. Existing scheduler processes weren't cleaned up between scheduler starts.
This could potentially cause multiple schedulers to run after sleep/waking your Mac

Would appreciate your feedback on this one @SRWieZ
NativePHP/electron#245

[SRWieZ]

Still get the error daily and that the number one issue that bother me so count on me to look at it ^^

[SRWieZ]

I'll comment here to keep track of our attempts to find a solution.

---

Both of those errors are kinda "related"

EPIPE stands for "Broken Pipe" - it occurs when your application tries to write data to a stream, socket, or process that has already been closed or terminated on the receiving end.

EBADF occurs when your application tries to perform an operation (read, write, close, etc.) on a file descriptor that is invalid, already closed, or doesn't exist.

I'm not sure which stream/connection is broken during macOS sleep.

I tried closing everything before sleep and reopening after, but that didn't help: https://github.com/NativePHP/electron/pull/207/files

[gwleuverink]

Thanks for the info! I'm now also hitting the EPIPE error.

I added a guard clause and haven't hit the error since.

The only time I get the error now is by running composer native:dev and then killing the process.

This does not occur when I use artisan serve or in my build.. yet 🤞🏻

I found out concurrently (which is used in native:dev) uses kill-sync too. Could it be kill-sync tries to enumerate process trees that contain dead/zombie processes?

[gwleuverink]

hmm composer native:dev also raises this error when I replace killSync in our codebase.

I know this is not the the issue you raised here, but the error is exactly the same.