Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0a7
2018.3.0b12
2019.1.0a1
Issue ID
1105514
Regression
Yes
Unity Crashes on GC_win32_get_memObject when allocating a lot of objects
How to reproduce:
1. Open user's attached project
2. Open and launch scene "Samplescene"
3. Select cube gameObjects under "MemoryChunk" GO inside the hierarchy
4. Duplicate those cubes
- Observe crash and "Fatal error in GC (Too many heap sections)" error
Reproducible with: 2018.3.1f1, 2019.1.0a12
Not reproducible with: 2017.4.17f1, 2018.2.20f1, 2018.3.0a6
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
This is a duplicate and fix is on way into 2018.3