Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1
2019.2.21f1
2019.3
2020.1
2020.2
Issue ID
1227607
Regression
No
[macOS] Editor crashes when trying to access audio capture devices
Reproduction steps:
1. Open user attached project
2. Open Scene "MiniCam" (Assets/NatDevice/Examples/MiniCam)
3. Audio capture devices are being accessed in MediaDeviceQuery.cs (95; 102)
4. Open MediaDeviceQuery.cs (note 1) on line 57Comment out devices.AddRange(WebCamDevices())
5. Enter Play Mode
6. Don't allow a microphone access
===Crash occurs===
Reproducible with: 2019.1.0a10, 2019.2.21, 2019.3.8f1, 2020.1.0b5, 2020.2.0a7
Not reproducible with: 2019.1.0a1
Not sure if this regression or not, I cloud not reproduce the crash with 2019.1.0a1 once, but after that testing higher versions when Unity asks developers tools access and Unity is added to the privacy setting, after that, it crashes all the time.
Regression might be in 2019.1.0a1-2019.1.0a10
IMPORTANT: when testing NEVER Allow Unity to access the microphone or you will not be able to use that device for testing anymore. If Unity asked for microphone permission it means that the issue did not reproduce (in that case just turn off the window).
Notes:
- Step 4 is needed because accessing Cameras also causes a crash due to the absence of permission request, and this is a known issue
- If in earlier versions you allowed Unity to access microphone at least once, it will not crash anymore, and resetting default permissions for microphone makes Unity always crash
- When attempting to enter Play mode in 2018.4.20f1, Unity asks for permission to access developer tools (iirc) and, after providing the computer password, Unity freezes, but does not crash. Unity did not ask to access the microphone, either
Stack frames:
#0 0x007fff641a3bea in __abort_with_payload
Thread 0x70000f39b000 may have been prematurely finalized
#1 0x007fff641a5525 in os_channel_create_extended.cold.1
Thread 0x70000f39b000 may have been prematurely finalized
#2 0x007fff5c2f75a7 in TCCAccessRequestIndirect
Thread 0x70000f39b000 may have been prematurely finalized
#3 0x007fff5c2f5545 in __TCCAccessCheckAuditToken_block_invoke
Thread 0x70000f39b000 may have been prematurely finalized
#4 0x007fff5c2f5a6c in __tccd_send_message_block_invoke
Thread 0x70000f39b000 may have been prematurely finalized
#5 0x007fff64289a08 in _xpc_connection_reply_callout
Thread 0x70000f39b000 may have been prematurely finalized
#6 0x007fff64289990 in _xpc_connection_call_reply_async
Thread 0x70000f39b000 may have been prematurely finalized
#7 0x007fff63fea578 in _dispatch_client_callout3
Thread 0x70000f39b000 may have been prematurely finalized
#8 0x007fff64001080 in _dispatch_mach_msg_async_reply_invoke
Thread 0x70000f39b000 may have been prematurely finalized
#9 0x007fff63ff948c in _dispatch_kevent_worker_thread
Thread 0x70000f39b000 may have been prematurely finalized
#10 0x007fff64244744 in _pthread_wqthread
Thread 0x70000f39b000 may have been prematurely finalized
#11 0x007fff64243827 in start_wqthread
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Resolution Note (2020.1.X):
This issue is caused by a crash in this plugin https://assetstore.unity.com/packages/tools/integration/natdevice-media-device-api-162053 which the author has recently fixed several of. I would recommend posting on this forum thread https://forum.unity.com/threads/natdevice-media-device-api.374690/ as there is a current known crash the author has reported to Apple.