Search Issue Tracker


Fixed in 2022.2.1f1, 2023.1.0a21



Found in




Issue ID




Crashes on "__pthread_kill" when trying to run the Editor tests on a different machine using ssh in batchmode and the main machine has been rebooted and the user is not logged in



Reproduction steps:

# Extract the attached project on M1 Mac
# Reboot the M1 Mac by pasting this command “sudo /usr/bin/fdesetup authrestart” in the Terminal
# Open a terminal or command window on another machine and enter “ssh user@ip-address "/Editor Path/" -runTests -nographics -batchmode -projectPath "Project path" -logFile -”

Expected result: The Editor runs fine and tests are executed
Actual result: The Editor crashes

Reproducible with: 2022.1.0a16, 2022.1.18f1, 2022.2.0b9, 2023.1.0a12
Not reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.0a15

Reproducible on: M1 MacOS 12.4 (21F79)

Note: The issue is reproducible on both Intel and Apple Silicon Editors on M1 Mac

First few lines of the stack trace when ran using the Apple Silicon Editor:
#0 0x0000018dab6d98 in __pthread_kill
#1 0x231280018da26340 in abort
#2 0xe92980018daa6b08 in __cxxabiv1::__aligned_malloc_with_fallback(unsigned long)
#3 0x864580018da96950 in demangling_unexpected_handler()
#4 0x2c7080018d98c320 in _objc_terminate()
#5 0x4f1380018daa5ea4 in std::__terminate(void (*)())

First few lines of the stack trace when ran using the Intel Editor (under Rosetta):
#0 0x007ff8101ff00e in __pthread_kill
#1 0x007ff810180d24 in abort
#2 0x007ff8101f1082 in abort_message
#3 0x007ff8101e21bd in demangling_unexpected_handler()
#4 0x007ff8100df00e in _objc_terminate()
#5 0x007ff8101f04a7 in std::__terminate(void (*)())

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.