This is likely due to 19c8ed5, but I haven't been able to fully pin it down.

Essentially, in the latest version of workerd, connecting, disconnecting, and then reconnecting to the inspector causes a segmentation fault:

workerd/util/symbolizer.c++:96: 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 #11: Segmentation fault: 11
stack: 

It's pretty easy to reproduce. Run:

npx workerd@latest serve samples/helloworld/config.capnp --inspector-addr=localhost:8989

and open up https://devtools.devprod.cloudflare.dev/js_app?ws=localhost:8989/main. Reloading that webpage twice will result in a segmentation fault.

the same problem doesn't present with the previous version of workerd:

npx workerd@1.20240806.0 serve samples/helloworld/config.capnp --inspector-addr=localhost:8989