Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
1045111
Regression
No
Heavy memory leak on creating 2D Array
How to reproduce:
1. Open the user-submitted project
2. Create a new empty game object and attach the MapGenerator script
3. In the Inspector Window change the values of "Width" and "Height"
4. Observe the Task Manager
Expected result: The values are inputted correctly
Actual: Unity leaks memory and freezes
Reproduced in: 2018.3.0a1, 2018.2.0b7, 2018.1.4f1, 2017.4.5f1, 2017.2.3f1, 2017.1.4p1
Note: Changing the Scripting runtime did not have any effect
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment