Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0b18
2023.3.0a14
Issue ID
UUM-55684
Regression
No
Crash on __pthread_kill when building a specific project
Reproduction steps:
1. Open the attached project “ReproCrash”
2. File > Build Settings > Build
Expected result: Player is built
Actual result: Editor crashes
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a14
Reproducible on: macOS 13.6 (M1 Max), macOS 14.0 (Intel)
Not reproducible on: Windows 10
First few lines of stack trace:
#0 0x0000018708c744 in __pthread_kill
#1 0x541a800186fd1ae8 in abort
#2 0x46000029d6a01f4 in monoeg_g_printv
#3 0x0000029d68560c in mono_log_write_logfile
#4 0x0000029d6a040c in monoeg_g_logv_nofree
#5 0x0000029d6a04c8 in monoeg_assertion_message
#6 0x0000029d6a0528 in monoeg_log_default_handler
#7 0x0000029d5f3fa8 in mono_marshal_get_native_wrapper
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thanks for reporting this issue. It looks like the code in this project which crashes is using COM in TouchInputField.cs, which Unity does not support.
Unfortunately Unity does not provide a good error message in this case to help you understand that limitation though! I wish that were better, but we've not found a good way to indicate that.
I'll close this bug, as it is not something we support. Please let me know if you have any questions about this issue. Thanks again!
Resolution Note (2023.3.X):
Thanks for reporting this issue. It looks like the code in this project which crashes is using COM in TouchInputField.cs, which Unity does not support.
Unfortunately Unity does not provide a good error message in this case to help you understand that limitation though! I wish that were better, but we've not found a good way to indicate that.
I'll close this bug, as it is not something we support. Please let me know if you have any questions about this issue. Thanks again!