SIGTERM leads to SIGABRT and SIGSEGV

[kpamnany]

When shutting down our server, we get a SIGTERM (on purpose), which outputs a backtrace (we may want to prevent this with a flag since SIGTERM is supposed to be graceful shutdown; related issue: #41057), which is partially reproduced below (read bottom to top):

This then cascades:

I haven't figured out what is happening here, but maybe somebody has seen this and knows a way to deal with it?

[gbaraldi]

Is this threaded code? Though segfaulting at exit isn't something julia isn't known to do.

[ararslan]

I'm not sure whether this is the same issue, if not then I can open a separate one. On an M1 Mac with the official 1.10.0-beta3 binary, I reliably get a segfault by launching a Julia REPL, ]update, backspace, ctrl+d:

$ julia-1.10
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.10.0-beta3 (2023-10-03)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

(@v1.10) pkg> update
    Updating registry at `~/.julia/registries/Beacon`
    Updating git-repo `[redacted]`
    Updating registry at `~/.julia/registries/General.toml`
  No Changes to `~/.julia/environments/v1.10/Project.toml`
  No Changes to `~/.julia/environments/v1.10/Manifest.toml`

julia>

[7550] signal (11.2): Segmentation fault: 11
in expression starting at none:0

It doesn't happen if I don't run ]update, or if I use exit() instead of ctrl+d. I also can't reproduce this on an Intel Mac with 1.10, M1 Mac with 1.9, nor M1 Mac with current master.