[BUG] Segmentation fault

OS: [e.g. Windows Client, Windows Server, or Linux Server] Ubuntu 20 (oracle arm cloud host,)
Valheim Game Version: [e.g. 0.4.11, etc] mistlands
V+ Mod Version: [e.g. 0.9, 0.9.2, etc.] 0.9.9.11 Describe the bug Segmentation fault when I run sudo ./start_server_bepinex.sh server_start.sh works fine and server starts and is reachable.

A clear and concise description of what the bug is and how you found it. Happens on starting bepnex.sh.

buntu@Foundry:~/Steam/Steamapps/common/valserv$ sudo ./start_server_bepinex.sh
ERROR: ld.so: object 'libdoorstop_x64.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Dynarec for ARM64, with extension: ASIMD AES CRC32 PMULL ATOMICS PageSize:4096
Box64 with Dynarec v0.1.9 098317e built on May  2 2022 17:21:44
Using default BOX64_LD_LIBRARY_PATH: ./:lib/:lib64/:x86_64/:bin64/:libs64/
Using default BOX64_PATH: ./:bin/
Counted 28 Env var
BOX64 try to Preload libdoorstop_x64.so
Looking for /home/ubuntu/Steam/Steamapps/common/valserv/valheim_server.x86_64
argv[1]="-name"
argv[2]="GAvatar"
argv[3]="-password"
argv[4]="AvataR"
argv[5]="-port"
argv[6]="2456"
argv[7]="-world"
argv[8]="GuildAvatar"
argv[9]="-public"
argv[10]="1"
argv[11]="-savedir"
argv[12]="/root/.config/unity3d/IronGate/Valheim"
Using emulated /home/ubuntu/Steam/Steamapps/common/valserv/doorstop_libs/libdoorstop_x64.so
Using native(wrapped) libc.so.6
Using native(wrapped) ld-linux-x86-64.so.2
Using native(wrapped) libpthread.so.0
Using native(wrapped) librt.so.1
Using emulated UnityPlayer.so
Using native(wrapped) libm.so.6
Using emulated /lib/x86_64-linux-gnu/libgcc_s.so.1
Using native(wrapped) libdl.so.2
Found UnityPlayer, hooking into it instead
4236|SIGSEGV @0xffffa6a1a610 (???(0xffffa6a1a610)) (x64pc=0xffffa6de9fd7//home/ubuntu/Steam/Steamapps/common/valserv/doorstop_libs/libdoorstop_x64.so:"/home/ubuntu/Steam/Steamapps/common/valserv/doorstop_libs/libdoorstop_x64.so/check_rel", rsp=0xffffa60770c8, stack=0xffffa5878000:0xffffa6078000 own=(nil) fp=0xffffa6077158), for accessing 0x1856d0 (code=1/prot=0), db=0x75b5e940(0xffffa6a1a5d4:0xffffa6a1a77c/0xffffa6de9fb3:0xffffa6dea047//home/ubuntu/Steam/Steamapps/common/valserv/doorstop_libs/libdoorstop_x64.so/check_rel:clean, hash:980bcde/980bcde) handler=(nil)
Segmentation fault (core dumped)

To Reproduce install on oracle cloud service and run

Steps for the devs to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior Run modded val A clear and concise description of what you expected to happen.

Troubleshooting

What steps have you taken to try to fix?

Screenshots

If applicable, add screenshots to help explain your problem.

Link to pastebin containing .cfg configuration if applicable:

Additional context

Please list any other mods besides V+ that you have installed here. Add any other context about the problem here.

Also receiving a segfault, though with the client, and not the server.

OS: [e.g. Windows Client, Windows Server, or Linux Server] Arch Linux 6.6.8-arch1-1
Valheim Game Version: [e.g. 0.4.11, etc] 0.217.38
V+ Mod Version: [e.g. 0.9, 0.9.2, etc.] 0.9.9.11

$ ./start_game_bepinex.sh 
Found UnityPlayer, hooking into it instead
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-allocator-temp-initial-block-size-main=262144"
    "memorysetup-allocator-temp-initial-block-size-worker=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"
zsh: segmentation fault (core dumped)  ./start_game_bepinex.sh

It outputs a coredump, which produces the following:

$ coredumpctl dump 13386 
           PID: 13386 (valheim.x86_64)
           UID: 1000 (myuser)
           GID: 1000 (myuser)
        Signal: 11 (SEGV)
     Timestamp: Tue 2023-12-26 15:55:55 EST (13min ago)
  Command Line: /home/myuser/.local/share/Steam/steamapps/common/Valheim/valheim.x86_64
    Executable: /home/myuser/.local/share/Steam/steamapps/common/Valheim/valheim.x86_64
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (myuser)
       Boot ID: 299f1522ffd64957afca87ade2f1a6b0
    Machine ID: 20a46e2eeef54336a1397e9c87f3dcb2
      Hostname: myhost
       Storage: /var/lib/systemd/coredump/core.valheim\x2ex86_64.1000.299f1522ffd64957afca87ade2f1a6b0.13386.1703624155000000.zst (present)
  Size on Disk: 940.1K
       Message: Process 13386 (valheim.x86_64) of user 1000 dumped core.

                Module /home/myuser/.local/share/Steam/steamapps/common/Valheim/valheim_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so without build-id.
                Module /home/myuser/.local/share/Steam/steamapps/common/Valheim/valheim_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
                Stack trace of thread 13386:
                #0  0x0000000000000000 n/a (n/a + 0x0)
                #1  0x00007f7e64446328 n/a (/home/myuser/.local/share/Steam/steamapps/common/Valheim/valheim_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so + 0x46328)
                #2  0x00007f7e645e53fe n/a (/home/myuser/.local/share/Steam/steamapps/common/Valheim/valheim_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so + 0x1e53fe)
                ELF object binary architecture: AMD x86-64

My system's log journal also produces the following message before the core dump occurs:

Dec 26 15:55:55 myhost (sd-parse-elf)[13428]: Could not parse number of program headers from core file: invalid `Elf' handle

If you'd like, I can take a look at getting you the entire coredump archive

valheimPlus / ValheimPlus

[BUG] Segmentation fault #739