Search Issue Tracker

Fixed

Fixed in 1.8.24

Votes

0

Found in [Package]

1.8.21

Issue ID

BUR-2874

Regression

Yes

Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument

Package: Burst

-

How to reproduce:
1. Create and open a new project with the “Universal 3D” template
2. Close the Editor
3. Open the Terminal
4. In the Terminal navigate to the project folder
5. Open the project from a command line with these arguments: “'Unity application path' -quit -batchmode -nographics -stackTraceLogType None -disableManagedDebugger -buildTarget OSXUniversal -projectPath .”
6. Observe the crash

Reproducible with: 2023.1.0a22, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Not reproducible with: 2023.1.0a21

Reproducible on: macOS 15.5 (M1 Max)
Not reproducible on: Windows 11

Notes:
- Issue does not reproduce if "-disableManagedDebugger" argument is removed
- Before the stack trace an error is thrown: “mono_os_mutex_trylock: pthread_mutex_trylock failed with "Invalid argument" (22)”

First few lines of stack trace:
#0  0x0000018ffad388 in __pthread_kill
#1  0x0000018feefc60 in abort
#2  0x000001388a007c in monoeg_g_printv
#3  0x00000138885494 in mono_log_write_logfile
#4  0x000001388a0294 in monoeg_g_logv_nofree

  1. Resolution Note (fix version 1.8.24):

    This issue will be fixed in the next release of Burst. Thank you for logging it.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.