fix(deploy): MemoryDenyWriteExecute=true core-dumps Node 24 at V8 isolate init#174
Open
tudorsaitoc wants to merge 1 commit into
Open
fix(deploy): MemoryDenyWriteExecute=true core-dumps Node 24 at V8 isolate init#174tudorsaitoc wants to merge 1 commit into
tudorsaitoc wants to merge 1 commit into
Conversation
…t isolate init The shipped unit sets MemoryDenyWriteExecute=true, which denies the writable+executable mprotect V8 needs when creating the first isolate. On Node 24 (the documented runtime) the service never reaches main(): # Fatal error in , line 0 # Check failed: 12 == (*__errno_location ()). ... v8::base::OS::SetPermissions ... v8::Isolate::Initialize Main process exited, code=dumped, status=5/TRAP Observed deploying the unit verbatim on Ubuntu / Node 24.15.0. Turn the directive off with a comment explaining why, so the next operator doesn't rediscover this from a core dump.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The shipped systemd unit sets
MemoryDenyWriteExecute=true, which denies the writable+executablemprotectV8's JIT needs when creating the first isolate. On Node 24 (the documented runtime) the service never reachesmain():Hit this deploying the unit verbatim on Ubuntu with Node 24.15.0 (repro:
systemctl --user enable --now gas-city-dashboard.serviceon any host, the service core-dumps before binding). This PR flips the directive to=falsewith a comment explaining why, so the next operator doesn't have to rediscover it from a core dump. Every other hardening directive is kept.Sibling data point from the same deploy landed on #88 (cold formulas/feed scan timing).