Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2021.1.0a10
2021.1.0b1
Issue ID
1301071
Regression
Yes
[OSX] Editor crashes on _pthread_cond_wait when launching editor with -importPackage command line argument
Steps to reproduce:
1. Download attached "test.unitypackage" (or use any other .unitypackage file)
2. Launch Unity editor with "-importPackage" command line argument with path to "test.unitypackage"
"/Applications/Unity/Hub/Editor/2021.1.0b1/Unity.app/Contents/MacOS/Unity" -createProject /Users/USER_NAME/Downloads/test -importPackage /Users/USER_NAME/Downloads/test.unitypackage
Reproduced with: 2021.1.0a10, 2021.1.0b1
Didn't reproduce with: 2021.1.0a9, 2020.2.0f1, 2019.4.17f1, 2018.4.30f1
Only reproduced on macOS
Note: reproduces with any .unitypackage file, importing works as expected in editor (without using the -importPackage command line argument)
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (fix version 2021.1):
Fixed crash in pthread_wait_cond when launching Unity with -importPackage option