Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
Issue ID
1126214
Regression
No
Memory Leak in MonoScript is caused by creating a nested Class that is inside of a Namespace
How to reproduce:
1. Download the user-submitted script(MemoryTest.cs)
2. Create a new Unity project
3. Import and attach the script onto any GameObject
4. Enter Play Mode
5. Open Window > Analysis > Profiler and select the Detailed Memory profiler
6. Take a sample from the Editor and see Scene Memory > MonoScript
Expected result: no memory leak occurs
Actual result: a memory leak occurs
Reproducible with: 2017.4.22f1, 2018.3.7f1, 2019.1.0a7
Not reproducible with: 2019.1.0a8, 2019.1.0b5, 2019.2.0a7
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
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Memory leak warnings are constantly thrown when Generating Font Atlas in Font Asset Creator with 4096x8192 Atlas Resolution
- “Glyph rendering has been aborted due to sampling point size” Log is printed and Font Atlas is not generated when Atlas Resolution is 8192x8192, and the Render Mode is SDF
This is a duplicate of issue #1085304