Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
0
Found in
2017.4
2018.4
2019.3
2019.3.3f1
2020.1
2020.2
Issue ID
1224501
Regression
No
Memory leak in Line Renderer when build is running in batchmode
Reproduction steps:
1. Open the attached project "1224501.zip"
2. Build the project
3. Run the built project from Terminal/Power Shell/Command Prompt with the -batchmode command line argument
4. Observe the memory usage of the built project from System Monitor/Task Manager
Actual results: Gradual increase in memory usage when compared running the same build without -batchmode
Reproducible with: 2017.4.39f1, 2019.3.9f1, 2020.1.0b6, 2020.2.0a7
Note: Reproducible on Mac
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b10
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.15f1
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.24f1