Open emichael opened 1 month ago
v20.17.0 is not the latest version. If you can reproduce in v20.18.0, please let me know, and include a minimal reproduction, without the need of external dependencies.
Yes it is reproducible in v20.18.0. No, I can't provide any other means of reproduction. I can send a core dump, though. I'm not a node dev and don't want to spend any more time on this.
Please send a core dump if you can.
Please send a core dump if you can.
We're experiencing this issue regularly in MDN's GitHub workflows since moving from Node.js 18 to 20 (see here and here from today).
@anonrig Would you know how we can gather a core dump from these failed workflow runs?
@caugner It looks to me like you're facing https://github.com/nodejs/node/issues/51555, which is results in the same Fatal message as this issue, but the stack trace is quite different. Maybe take a look at that issue instead for workarounds.
Version
v20.17.0
Platform
Subsystem
No response
What steps will reproduce the bug?
docker run ghcr.io/immich-app/immich-server:v1.117.0
How often does it reproduce? Is there a required condition?
It is 100% reproducible on my system. The error happens ~immediately.
What is the expected behavior? Why is that the expected behavior?
It shouldn't crash.
What do you see instead?
Additional information
This was previously reported in https://github.com/immich-app/immich/issues/12133. Both the original reporter and I are running in a similar environment (Docker/Debian-based VM/bhyve/FreeBSD/Ryzen CPU).