Search Issue Tracker
Duplicate
Votes
6
Found in
2018.3.0b3
Issue ID
1086743
Regression
No
Editor crashes with GC_win32_get_mem when Serializable object has a reference to other System.Serialized object
How to reproduce:
1. Open attached "FirepowerAI" project
2. Load Scene "CoverTest" under Assets/FirepowerAI/Scenes
3. Select "Map" object in Hierarchy and click button "Build Cover Nodes" in Inspector
4. Enter Play Mode
Expected result: Editor does not crash
Actual result: Editor crashes
Reproduced with: 2018.3.0b5, 2019.1.0a3
Could not reproduce with earlier major versions of Unity because of compilation errors
Notes: Editor spams a lot of Fatal error windows "Too many heap sections".
Comments (2)
-
Peter77
Oct 23, 2018 19:09
Related forum thread:
https://forum.unity.com/threads/case-1092711-crash-with-too-many-heap-on-gc.571906/ -
cygnusprojects
Oct 23, 2018 18:18
'Too many heap sections' also turned up in my testing of the 2018.3 beta.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Duplicate issue. This has been fixed for 2018.3