Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.0a6
2018.3.0a5
Issue ID
1062813
Regression
Yes
Unity crashes on std::deque<InputEvent,std::allocator<InputEvent> >::erase when using SetParent on a large amount of GameObjects
Repro steps:
1. Open attached project
2. Open scene "Scene"
3. Enter Play Mode
4. Press the "+10000" button in the Game View (might crash on this step)
5. Unpause the Play Mode and repeat step 4 several times
6. Exit Play Mode
Expected: Unity exits Play Mode
Actual: Unity throws StackOverflowException and crashes
Reproducible with: 2018.1.0a6, 2018.1.9f1, 2018.2.1f1, 2018.3.0a5
Not reproducible with: 2017.2.3p2, 2017.4.8f1
Notes:
- On some versions, bug reporter doesn't pop up
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note (2020.2.X):
I can't reproduce this in 2020.2. I don't know what the fix is.