Search Issue Tracker
Duplicate
Votes
10
Found in
2017.2.0f3
Issue ID
968422
Regression
No
Editor crashes when entering/leaving play mode on .NET 4.6
Reproduction steps:
1. Open project attached (UnityTestBug.zip).
2. Open scene TestBug (Assets/FindBug/TestBug)
3. Press Menu/Test/Start
Result: Unity will crash in about 5 minutes. Might take a bit longer on the latest versions.
Reproduced on: 2017.2.0p2, 2017.3.0b9, 2018.1.0a3.
Comments (3)
-
ugen_oak
Nov 14, 2017 21:40
Agreed on reprioritizing this. I am experiencing ~10 crashes daily, as is everyone else on my team. This is presenting a significant disruption to our workflow.
-
CriDos
Nov 13, 2017 18:35
I will add information: https://github.com/CriDos/UnityTestBug
-
CriDos
Nov 13, 2017 18:26
I will add information:
The frequency of crashes in a real and large project is much higher than in the test.
For a day of constant work in the editor of 12-20 crashes - is stable.
So I advise you to reconsider the priority;)
Thank you.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #967206