Project Zomboid Server : Fails to start

[FerLuisxd]

What Game Project Zomboid Server (steamid: 380870 ), installed through the steamcmd

Describe the bug Trying to start the server would get a java crash

To Reproduce Steps to reproduce the behavior:

1. FEXBash
2. Go to the installed location of project zomboid server (Steam/steamapps/common/Project\ Zomboid\ Dedicated\ Server)
3. Start it ./start-server.sh -servername pzserver

Expected behavior The server should start correctly

Screenshots and Video

System information:

• OS: Ubuntu 22.04
• CPU/SoC: Ampere 4 cpu ARM64
• RootFS used: Ubuntu 22.04 Official Rootfs
• FEX version: FEX-2211
• Thunks Enabled: No

Additional context

• Is this an x86 or x86-64 game: x86
• Does this reproduce on x86-64 host with FEX: Untested
• Does this reproduce on AArch64 with Radeon/Intel/Nvidia: Untested
• Is this a Vulkan game: No
  • If Yes, What is your Vulkan driver:

Add any other context about the problem here. This is an oracle cloud computer

[Sonicadvance1]

This is a known issue with trying to run Java applications under FEX. This requires robust state reconstruction for java's exception handling to work.

[EL-S]

This is a known issue with trying to run Java applications under FEX. This requires robust state reconstruction for java's exception handling to work.

Is that likely to ever be implemented?

[Sonicadvance1]

At some point it will be implemented but it is fairly low priority since most applications don't need full state reconstruction.

[Guztaver]

Some update on this? Now I crashed in the character creation menu, while trying to connect into the server logs: https://controlc.com/427d036b (hs_err_pid6249) https://controlc.com/001f8d9c (PZ-Log)

[RGdevz]

tried this few days ago, its behaved good but after about 15 mins got segfault hs_err_pid1546.log

[Sonicadvance1]

From that crash dump: Instruction at RIP: cmp rax,QWORD PTR [rbx+rcx*1] RBX: 0x00000008_6172_7420 RCX: 0x0000000000000038 Accessed address: 0x00000008_6172_7458

Which is a memory region that isn't mapped in the process. Looks like potentially some state corruption earlier in the process for RBX to be pointing to incorrect memory. Interesting, but doesn't shed any light on why it got that way.