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
In the same vein as #8673, when trying to run Parcel in an AWS Lambda environment, the threads crash with the following error due to invalid execArgv flags being passed:
Error [ERR_WORKER_INVALID_EXEC_ARGV]: Initiated Worker with invalid execArgv flags: --expose-gc, --max-semi-space-size=17"
davidjb
changed the title
Worker threads crash on AWS Lambda when unexpected execArgv are passed
Worker threads crash if --expose-gc or --max-semi-space-size are passed in execArgvNov 23, 2023
🐛 bug report
In the same vein as #8673, when trying to run Parcel in an AWS Lambda environment, the threads crash with the following error due to invalid execArgv flags being passed:
The environment for Node Lambda execution isn't openly published but the current implementation script for
node20.x
is available at https://gist.github.com/davidjb/432ea4e1c89f399ec412270539fe126f, showing the extent of Node options that might be passed, including:--max-semi-space-size
(breaks)--max-old-space-size
(ok)--expose-gc
(breaks)--max-http-header-size
(ok)🎛 Configuration (.babelrc, package.json, cli command)
test.js
:Ensure
@parcel/core
is installed and then runnode --expose-gc --max-semi-space-size=17 test.js
to experience the worker crashes.🤔 Expected Behavior
To run successfully without crashing
😯 Current Behavior
💁 Possible Solution
So given the solution to #8673, perhaps filter the two breaking execArgv flags again.
I've opened PR #9399 with just that.
🔦 Context
Run Parcel in a Node AWS Lambda environment (
node20.x
)💻 Code Sample
See Configuration section above.
🌍 Your Environment
The text was updated successfully, but these errors were encountered: