Problems with Unity 2021.3.1f1 (Silicon) - Namespace SIGNAL, Code 4 Illegal instruction: 4

Question

Level 1

4 points

Problems with Unity 2021.3.1f1 (Silicon) - Namespace SIGNAL, Code 4 Illegal instruction: 4

I have a project in Unity that is crashing during the Asset import, but only when I try to use a particular SDK. The error I'm getting is the one above - more text below. The project builds and runs just fine until I try to import this one particular asset, but then it crashes and corrupts one of the files involved.

The reasons I think this is actually an Apple problem are

1) That the SDK developers say they've never seen this happen before, and

2) The error message shows up in a lot of other discussions like this one: after installing Catalina, one app keeps … - Apple Community

3) Buried deep in the crash report, it looks like maybe a bad HTTP request had something to do with the crash, but a bad HTTP request shouldn't cause the whole program to crash.

Error Report excerpts:

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process: Unity [3879]

Path: /Applications/Unity/*/Unity.app/Contents/MacOS/Unity

Identifier: com.unity3d.UnityEditor5.x

Version: Unity version 2021.3.1f1 (2021.3.1f1)

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

Responsible: Unity Hub [89674]

//skipping some stuff

Crashed Thread: 0 tid_103 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGILL)

Exception Codes: KERN_PROTECTION_FAILURE at 0x000000016e73fff0

Exception Codes: 0x0000000000000002, 0x000000016e73fff0

Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4

Terminating Process: Unity [3879]

VM Region Info: 0x16e73fff0 is in 0x16af3c000-0x16e740000; bytes after start: 58736624 bytes before end: 15

REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL

VM_ALLOCATE 16aecc000-16af0c000 [ 256K] rwx/rwx SM=PRV

GAP OF 0x30000 BYTES

---> STACK GUARD 16af3c000-16e740000 [ 56.0M] ---/rwx SM=NUL ... for thread 0

Stack 16e740000-16ef3c000 [ 8176K] rw-/rwx SM=PRV thread 0

Kernel Triage:

VM - Compressor failed a blocking pager_get

//repeated a few times

Thread 0 Crashed:: tid_103 Dispatch queue: com.apple.main-thread

0 ??? 0x2e60c13c8 ???

//a whole lot more lines like this

//a bunch of stack trace stuff about Semaphore and Job Workers

//and some more from the crash report:

Thread 40:: Loading.AsyncRead

0 libsystem_kernel.dylib 0x1b8be9990 semaphore_wait_trap + 8

1 libdispatch.dylib 0x1b8a6713c _dispatch_sema4_wait + 28

2 libdispatch.dylib 0x1b8a677f4 _dispatch_semaphore_wait_slow + 132

3 Unity 0x1038a8e90 UnityClassic::Baselib_SystemSemaphore_Acquire(UnityClassic::Baselib_SystemSemaphore_Handle) + 28

4 Unity 0x10142c5c0 Semaphore::WaitForSignal(int) + 188

5 Unity 0x10158c68c AsyncReadManagerThreaded::ThreadEntry() + 240

6 Unity 0x10158bc50 AsyncReadManagerThreaded::StaticThreadEntry(void*) + 12

7 Unity 0x1019518b8 Thread::RunThreadWrapper(void*) + 1188

8 libsystem_pthread.dylib 0x1b8c25240 _pthread_start + 148

9 libsystem_pthread.dylib 0x1b8c20024 thread_start + 8

Thread 41:: HTTP REST Server

0 libsystem_kernel.dylib 0x1b8bf3d38 __select + 8

1 Unity 0x103893810 ns_mgr_poll + 560

2 Unity 0x1030a2440 RestService::HttpTransport::RunLoop() + 48

3 Unity 0x1019518b8 Thread::RunThreadWrapper(void*) + 1188

4 libsystem_pthread.dylib 0x1b8c25240 _pthread_start + 148

5 libsystem_pthread.dylib 0x1b8c20024 thread_start + 8

Thread 42:: REST Message Handler

0 libsystem_kernel.dylib 0x1b8be9990 semaphore_wait_trap + 8

1 libdispatch.dylib 0x1b8a6713c _dispatch_sema4_wait + 28

2 libdispatch.dylib 0x1b8a677f4 _dispatch_semaphore_wait_slow + 132

3 Unity 0x1038a8e90 UnityClassic::Baselib_SystemSemaphore_Acquire(UnityClassic::Baselib_SystemSemaphore_Handle) + 28

4 Unity 0x10142c5c0 Semaphore::WaitForSignal(int) + 188

5 Unity 0x10309d6a8 RestService::RestMessageHandler::Entry(void*) + 40

6 Unity 0x1019518b8 Thread::RunThreadWrapper(void*) + 1188

7 libsystem_pthread.dylib 0x1b8c25240 _pthread_start + 148

8 libsystem_pthread.dylib 0x1b8c20024 thread_start + 8

MacBook Pro 16″, macOS 12.2

Posted on May 5, 2022 12:26 PM

Reply

Answer 1

MrHoffman

Level 10

146,467 points

May 5, 2022 1:24 PM in response to juliaseid

Contact Unity app support. (Even if this is an Apple issue, Unity support will likely be more familiar with it than folks around here (as Unity questions here are quite rare) and also in the best position to either work around or fix this, or to suggest workarounds to you, and/or to work directly with Apple to fix this.)

Reply

Answer 2

juliaseid Author

Level 1

4 points

May 5, 2022 2:17 PM in response to MrHoffman

Thanks, you're probably right - and actually, whether it's a Unity issue, an Apple issue, or an SDK issue is all a little muddy, since it's likely an issue of how they all interact. Since I'm working directly with the SDK developers, I'm going back to them first.

Reply

Answer 3

etresoft

Level 9

56,680 points

May 8, 2022 7:15 AM in response to juliaseid

juliaseid wrote:

I have a project in Unity

...

I think this is actually an Apple problem

This is a project you are developing? How do you know it isn't your own bug?

1) That the SDK developers say they've never seen this happen before

Seen what? A crash? Crashes are common when developing software. It doesn't matter what SDK or platform you are using.

2) The error message shows up in a lot of other discussions like this one: after installing Catalina, one app keeps … - Apple Community

That is an app for reading the writing of Ellen G. White. I don't think it has anything to do with Unity games.

3) Buried deep in the crash report, it looks like maybe a bad HTTP request had something to do with the crash, but a bad HTTP request shouldn't cause the whole program to crash.

It looks like there was some internal communication going on at the same time as the crash. These cross-platform apps often run as self-contained clients and servers. Your app is essentially a web app run with a local web server. Each thread is usually a self-contained mini-process that has little to do with any other threads. Poorly-written multithreaded code is common, and that can causes crashes. However that is unlikely to be the case in a popular cross-platform app like this. The internal messaging system is probably pretty stable.

Unfortunately, in your crash report, you have gone to the trouble to edit out the only information that is relevant to the crash, "//a whole lot more lines like this".

Since you know exactly where it crashes, it should be relatively easy to debug. In theory, I would tell you to put a break point just before it loads this resources and step through the logic at that point. However, I don't know if any of that is possible in the Unity environment.

Good luck!

Reply

Problems with Unity 2021.3.1f1 (Silicon) - Namespace SIGNAL, Code 4 Illegal instruction: 4

Similar questions