Search Issue Tracker
Fixed
Votes
0
Found in
2017.3.1f1
Issue ID
1012562
Regression
No
Unity crashes/freezes when creating a new project with fully filled Project Name field
How to reproduce:
1. Open Unity
2. Create a new project with name "Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Te" (make sure that Project Name field is filled up till the end)
3. Receive Unity Package Manager Error and press continue
4. Unity crashes and must be killed with task manager because repeating 2 step is not working now because of multiple Unity instances
Expected result: A new project should be created
Actual result: Unity crashes and the new project is not created
Regression first introduced in:
Reproducible with: 2018.2.0a4, 2018.1.0b11, 2017.3.1p4, 2017.2.2f1, 2017.1.3p2, 5.6.5p2
Not reproducible with:
Note:
2017.3.1p4, 2017.1.3p2, 5.6.5p2 gives Failed to load windows layout error
2017.2.2f1 crashes instantly
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Fixed in Hub 2.0.0