[BUG] eXist-db 6.4.0 dmg ui crashes but cli runs

[ahenket]

Describe the bug
I downloaded the eXist-db 6.4.0 dmg for macOS. Opened the dmg and dragged the eXist-db.app to my Applications folder and double clicked from there. A dialog pops up that Apple could not verify existence of malware. Clicked "Done" and went into System Preferences > Privacy and Security to "Open anyway". After authentication eXist-db.app is reopened, and crashes.

Running the startup.sh from the command line works as expected.

Crash log text attached

eXist-db-6.4.0-crashlog.txt

Expected behavior
The expectation was that "Open anyway" would make the app start normally with the system configurator where you may set ports and such

To Reproduce
See description

Other things I've tried

• Remove all extended attributes from the dmg and/or the app
• Switch to Java version 8, 13, 19, 21 and 21GraalVM

Context

% xst info                                                                         
Build: eXist-6.4.0 (2e4182841b38317324877c0b2e1febcaa26ed83a)
Java: 21.0.7 (Oracle Corporation)
OS: Mac OS X 15.5 (aarch64)

% /usr/libexec/java_home -V
Matching Java Virtual Machines (7):
    21.0.7 (arm64) "Oracle Corporation" - "Java SE 21.0.7" /Library/Java/JavaVirtualMachines/jdk-21.jdk/Contents/Home
    21.0.2 (arm64) "Oracle Corporation" - "Oracle GraalVM 21.0.2+13.1" /Library/Java/JavaVirtualMachines/graalvm-jdk-21.0.2+13.1/Contents/Home
    19.0.2 (arm64) "Oracle Corporation" - "Java SE 19.0.2" /Library/Java/JavaVirtualMachines/jdk-19.jdk/Contents/Home
    13.0.14 (arm64) "Azul Systems, Inc." - "Zulu 13.54.17" /Library/Java/JavaVirtualMachines/zulu-13.jdk/Contents/Home
    1.8.451.10 (arm64) "Oracle Corporation" - "Java" /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
    1.8.0_402 (x86_64) "Eclipse Temurin" - "Eclipse Temurin 8" /Library/Java/JavaVirtualMachines/temurin-8.jdk/Contents/Home
    1.8.0_362 (arm64) "Azul Systems, Inc." - "Zulu 8.68.0.21" /Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home
/Library/Java/JavaVirtualMachines/jdk-21.jdk/Contents/Home

[dizzzz]

Hmmm, I see a signal 6 in the log...

checking https://hatchjs.com/signal-6-caught-application-halted/ :

What is Signal 6?

Signal 6 is also known as the “SIGABRT” signal. It’s a software interrupt that tells a program to stop running immediately. This can happen for a variety of reasons, such as a fatal error, a memory fault, or a hardware problem. When a signal 6 is received, the program will terminate without saving any of its state.

What Causes Signal 6?

There are a number of things that can cause signal 6. Some of the most common causes include:

Memory errors: If a program attempts to access memory that it doesn’t have permission to access, it will generate a signal 6 error.
Fatal errors: If a program encounters a fatal error, such as a division by zero, it will also generate a signal 6 error.
Hardware problems: If a hardware device fails, it can cause a signal 6 error. This is more common on older computers or computers with faulty hardware.
How to Fix Signal 6

If you’re experiencing signal 6 errors, there are a few things you can try to fix them.

Check your system for memory errors: The first thing you should do is check your system for memory errors. You can do this by running the Windows Memory Diagnostic Tool.
Update your drivers: If you’re using outdated drivers, they could be causing signal 6 errors. Make sure to update your drivers to the latest version.
Run a virus scan: A virus infection could also be causing signal 6 errors. Run a virus scan to make sure your computer is free of malware.
Reinstall the program: If you’re still experiencing signal 6 errors after trying the above solutions, you may need to reinstall the program. This will often fix any corruption that may be causing the errors.

[dizzzz]

Checking the log a bit more.... The failing process is called "eXist-JavaAppLauncher" {to be expected} , I read this that internally a VM_memory allocate is is failing:

my un-educated guess is that this is the native trace, where the 'trap' is done in the kernel, under "CoreFoundation":

no it is actually thread 4:

(leaving out the long thread stack) -> there is only native (macos and VM) code here.

[dizzzz]

just a hunch... did you configure siri/ Apple AI in a way?

[dizzzz]

Apple suggests to file a crash report: https://developer.apple.com/forums/thread/688669