An issue has been found where the editor aborts with exit code 134 during the initial asset import. It always happens while a texture with crunched compression is being compressed.

{{}}

./External/TextureCompressors/Crunch/crnlib/crn_threading_pthreads.cpp(194): Failure: "semaphore: sem_wait() or sem_timedwait() failed" Fatal error: Interrupted system call Caught fatal signal - signo:6 code:-6 ... #9 crnlib::task_pool::join() #11 crnlib::crn_comp::quantize_images() #13 crnlib::crn_comp::compress_pass(...) #17 CompressTextureWithMultipleImagesCrunch(...) #20 TextureImporter::GenerateAssetData(AssetImportContext&) #28 InitialRefreshV2(bool, bool) #29 Application::InitializeProject()

{{}}

The message says "Interrupted system call", so the wait gets interrupted and the compressor treats that as fatal and exits the editor.

We have been unable to reproduce this on our end, but this started appearing on 5.15.0-1116-azure. There have been reproduction steps provided:

Steps to reproduce:

1. Use a project with textures that have crunched compression enabled.
2. Delete the Library folder so the import runs cold, because crunch only runs on a cold import.
3. Run <UnityEditor> -batchmode -projectPath <project> -logfile <log> -nographics -quit
4. The attempt reproduces when the log contains crn_threading_pthreads.

Actual results: Editor aborts with exit code 134 around 90% of the time

Expected results: Project builds without issue