Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

🐛 BUG: wrangler errors in GitHub Actions "Received signal #11: Segmentation fault" #1075

Closed
remarkablemark opened this issue Aug 27, 2023 · 2 comments
Closed

🐛 BUG: wrangler errors in GitHub Actions "Received signal #11: Segmentation fault" #1075

remarkablemark opened this issue Aug 27, 2023 · 2 comments
Assignees
@irvinebroque
Labels
bug Something isn't working

Comments

@remarkablemark
Copy link

Which Cloudflare product(s) does this pertain to?

Wrangler core

What version(s) of the tool(s) are you using?

3.6.0 [Wrangler]

What version of Node are you using?

18.17.1

What operating system are you using?

Ubuntu 22.04

Describe the Bug

Wrangler versions 3.5.0-3.6.0 errors in GitHub Actions using the images ubuntu-20.04 and ubuntu-22.04:

Related to cloudflare/workers-sdk#3631

Please provide a link to a minimal reproduction

encrypit/encrypit#181

Please provide any relevant error logs

$ wrangler pages dev . --r2=EXPIRATION_DAYS_7

Compiling worker to "/tmp/functionsWorker-0.9707300519213211.mjs"...
✨ Compiled Worker successfully
 ⛅️ wrangler 3.6.0
------------------
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote
Using vars defined in .dev.vars
Your worker has access to the following bindings:
- R2 Buckets:
  - EXPIRATION_DAYS_7: EXPIRATION_DAYS_7
- Vars:
  - NODE_ENV: "(hidden)"
⎔ Starting local server...
[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-08-14",
but you've requested "2023-08-27". Falling back to "2023-08-14"...
workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
*** Received signal cloudflare/workers-sdk#11: Segmentation fault
stack: /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@16966b2 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1696605 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1686f8d /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1687693 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@168dcbc /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1691266 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@168f8ed /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@16807e6 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@16803b8 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1680194 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@168017c /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@326b86e /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@326b46d /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@3269758 /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@326951a /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@1671293 /lib/x86_64-linux-gnu/libc.so.6@29d8f /lib/x86_64-linux-gnu/libc.so.6@29e3f /home/runner/work/encrypit/encrypit/node_modules/@cloudflare/workerd-linux-64/bin/workerd@167102d
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
@remarkablemark remarkablemark added the bug Something isn't working label Aug 27, 2023
@1000hz 1000hz transferred this issue from cloudflare/workers-sdk Aug 28, 2023
@1000hz 1000hz removed this from workers-sdk Aug 28, 2023
@mrbbot
Copy link
Contributor

mrbbot commented Aug 28, 2023

Hey! 👋 I'm guessing this is the same issue as cloudflare/miniflare#651. We've reported this to the runtime team. 👍

ohodson added a commit that referenced this issue Aug 29, 2023
@ohodson
EW-7716: fix crashing race with InspectorService initialization
41c8939 
Fixes a race between initializing the InspectorService::isolates field
on the inspector service thread and
Server::InspectorServiceIsolateRegistrar::registerIsolate inserting an
isolate into the InspectorSerivce::isolates field on a worker thread.

This change ensures that the InspectorService instance is initialized before
worker threads can start registering isolates.

Test: manual check repro steps in
      cloudflare/miniflare#651
      no longer cause crashes.

Bug: #1075
Bug: cloudflare/miniflare#651
Bug: EW-7716
@ohodson ohodson mentioned this issue Aug 29, 2023
Merged
ohodson added a commit that referenced this issue Aug 29, 2023
@ohodson
EW-7716: fix crashing race with InspectorService initialization
068c90a 
Fixes a race between initializing the InspectorService::isolates field
on the inspector service thread and
Server::InspectorServiceIsolateRegistrar::registerIsolate inserting an
isolate into the InspectorSerivce::isolates field on a worker thread.

This change ensures that the InspectorService instance is initialized before
worker threads can start registering isolates.

Test: manual check repro steps in cloudflare/miniflare#651 no longer repro.

Bug: #1075
Bug: cloudflare/miniflare#651
Bug: EW-7716
ohodson added a commit that referenced this issue Aug 30, 2023
@ohodson
EW-7716: fix crashing race with InspectorService initialization
511e923 
Fixes a race between initializing the InspectorService::isolates field
on the inspector service thread and
Server::InspectorServiceIsolateRegistrar::registerIsolate inserting an
isolate into the InspectorSerivce::isolates field on a worker thread.

This change ensures that the InspectorService instance is initialized before
worker threads can start registering isolates.

Test: manual check repro steps in cloudflare/miniflare#651 no longer repro.

Bug: #1075
Bug: cloudflare/miniflare#651
Bug: EW-7716
ohodson added a commit that referenced this issue Aug 30, 2023
@ohodson
EW-7716: fix crashing race with InspectorService initialization
2e3e74e 
Fixes a race between initializing the InspectorService::isolates field
on the inspector service thread and
Server::InspectorServiceIsolateRegistrar::registerIsolate inserting an
isolate into the InspectorSerivce::isolates field on a worker thread.

This change ensures that the InspectorService instance is initialized before
worker threads can start registering isolates.

Test: manual check repro steps in cloudflare/miniflare#651 no longer repro.

Bug: #1075
Bug: cloudflare/miniflare#651
Bug: EW-7716
@remarkablemark
Copy link
Author

I am no longer seeing the error after upgrading wrangler to 3.7.0: encrypit/encrypit#194

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@irvinebroque irvinebroque

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@irvinebroque @remarkablemark @mrbbot