Fatal error: Check failed: is_clonable_js_type || is_clonable_wasm_type.

[Siegrift]

Version

v18.19.0

Platform

Linux 7b363bc59a8a 6.4.16-linuxkit #1 SMP PREEMPT Wed Oct 25 16:32:24 UTC 2023 aarch64 Linux

Subsystem

Docker deployed on AWS (node:18-alpine)

What steps will reproduce the bug?

Unfortunately, I don't have reliable steps to reproduce the issue.

How often does it reproduce? Is there a required condition?

Every few days (without any fixed schedule) my applications dies with a fatal error. There doesn't seem to be anything out of ordinary in the service.

What is the expected behavior? Why is that the expected behavior?

The check should be an invariant that never throws.

What do you see instead?

Fatal error in my application.

Additional information

I deploy my application on AWS and after a few days some fail with the same exact error:

#FailureMessage Object: 0x7fffc042afe0
#
#
#
# Check failed: is_clonable_js_type || is_clonable_wasm_type.
# Fatal error in , line 0
#

Based off the logs I don't see anything suspicious. The CPU and Memory usage graph on AWS are stable and have values 30% and 60% respectively. I looked at similar issues (https://github.com/lovell/sharp/issues/2205 and https://github.com/nodejs/help/issues/3743), but they have slightly different error. Based of my quick look I can see the failed check in the source code here and my guess is that this is some kind of a race condition.