Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.3.0a5
2018.4.0f1
2018.4.2f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1165974
Regression
Yes
[macOS] Opening a project with static StartUp() editor script through Terminal crashes Unity
To reproduce:
1. Open attached project "1165974.zip" through the terminal with "/Volumes/External/Applications/2018.4/Unity/Unity.app/Contents/MacOS/Unity -projectPath "/Users/*username*/Downloads/1165974"
Expected result: project is opened
Actual result: Unity crashes with 0 stack frames
Reproduced on:
2018.3.0a5 2018.4.3f1 2019.1.9f1 2019.2.0b8 2019.3.0a8
Not reproduced on:
2018.3.0a4
Notes:
- Getting an error in 2017.4.30f1
- Doesn't seem to be reproducing on Win10 machine
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
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note (fix version 2019.3):
Stop race condition when attempting to build player from a static C# object constructor.