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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note:
This is a duplicate and fix is on way into 2018.3