JASP 0.19.3 Crashes on macOS Sequoia (Apple Silicon): kevent64: Bad file descriptor

[ybence]

System Info

JASP version 0.19.3, both the Intel and M1 versions crashing on opening on my 2020 Mac Air M1. Launch method: Terminal with QTWEBENGINE_DISABLE_SANDBOX=1 Issue: Crash on launch with kevent64: Bad file descriptor (9) in QtWebEngine

JASP Module

Unrelated

Is there a specific analysis that caused the crash?

No response

Log files

Hi JASP team,

I'm encountering a crash on startup with JASP 0.19.3 on macOS Sequoia (version 15.5) running on an Apple Silicon (M1) MacBook Air.

I attempted launching via Terminal with sandboxing disabled (QTWEBENGINE_DISABLE_SANDBOX=1), but the application still crashes immediately. Below is the full terminal log output when trying to launch the app:

Making new argument list for Application startup: /Applications/JASP.app/Contents/MacOS/JASP
Starting JASP 0.19.3 from commit c8710df5442149527b0692cc1367ea5b3c982d04 and branch 0.19.3
QtWebEngineQuick initialized
Application initialized
Sandboxing disabled by user.
Path override failed for key base::DIR_APP_DICTIONARIES and path '/Applications/JASP.app/Contents/MacOS/qtwebengine_dictionaries'
Application init entered
MainWindow constructor started
TempFiles::createSessionDir(): '/Users/yasarbence/.JASP/temp/77921' about to be (removed and re)created.
...
qt.qpa.fonts: Populating font family aliases took 198 ms. Replace uses of missing font family ".AppleSystemUIFontMonospaced" with one that exists to avoid this cost.
[77921:90115:0514/111700.205942:ERROR:validation_errors.cc(117)] Invalid message: VALIDATION_ERROR_DESERIALIZATION_FAILED
[77921:90115:0514/111700.205980:ERROR:interface_endpoint_client.cc(702)] Message 1464847659 rejected by interface network.mojom.NetworkService
[77921:90115:0514/111700.246787:FATAL:message_pump_kqueue.cc(433)] Check failed: . kevent64: Bad file descriptor (9)
zsh: trace trap QTWEBENGINE_DISABLE_SANDBOX=1 /Applications/JASP.app/Contents/MacOS/JASP
...

Steps to Reproduce

Opening the app.

[github-actions]

@ybence, thanks for taking the time to create this report. Please upload to the issue website (#3444, attaching to an email does not work) the log files from JASP. For more information read our Logging Guide page to learn where to (and how to) find JASP log files.

[boutinb]

Hi @ybence, I have never tried on Mac Air, but I don't see why it should not work. Can you try also with Safe Graphics:
JASP --safeGraphics

[ybence]

Thank you for you response! Unfortunately, after trying to launch it with safeGraphics it still crashes. The crash is inside QtWebEngine with a kevent64 bad file descriptor. I’ve also tested the Intel version under Rosetta and older versions without success.
What should I do?

[boutinb]

Do you get the same error is you use QTWEBENGINE_DISABLE_SANDBOX or not?

[ybence]

I've tried with it while disabling the sandbox, but unfortunately, it still crashes. So far, I have tried:

• with --safeGraphics

• with --disable-gpu

• both Apple Silicon and Intel (Rosetta) builds

• Set QTWEBENGINE_DISABLE_SANDBOX=1

• Created a clean macOS user profile

• Fully uninstalled and reinstalled JASP

After all these, it still remains unsuccessful. An excerpt from the crash output is this:
FATAL:message_pump_kqueue.cc(433)] Check failed: . kevent64: Bad file descriptor (9)
zsh: trace trap QTWEBENGINE_DISABLE_SANDBOX=1 /Applications/JASP.app/Contents/MacOS/JASP

Would be glad if I managed to work around this problem.

[tomtomme]

@ybence
Until we find the root of the problem you could try https://static.jasp-stats.org/Nightlies/
Those are unstable / untested, but maybe they at least launch...

other probably obvious tipps:

• check how much disk space is left
• try after a fresh restart of the machine
• check for macOS updates. 15.5 is pretty new, but still there could be even more recent bug fixes by Apple

[boutinb]

In the output you send, there is this:
Path override failed for key base::DIR_APP_DICTIONARIES and path '/Applications/JASP.app/Contents/MacOS/qtwebengine_dictionaries'
which is quite worrying already.
There is apparently an incompatibility with the Qt WebEngine (the results of the analyses are displayed by this Qt WebEngine), and your system. I cannot see in the Qt documentation what could be wrong with Mac Book Air, but I can't test it because I don't have one. Do you have another laptop?