Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0f3
Issue ID
933145
Regression
Yes
Giving CanvasRenderer dynamic meshes creates a memory leak
Steps to reproduce:
1. Download the newest attached project("Repro.zip")
2. Enter Playmode
3. Open profiler
4. Look at memory usage
Result: memory leak
Reproduced on 2017.1.0a1, 2017.1.0f3, 2017.2.0b2, 2017.3.0a1
Not reproduced on 5.5.4f1, 5.6.2p4
Regression introduced in 2017.1.0a1
Comments (2)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
ifisch
Sep 09, 2019 20:59
Indeed. The "issue tracker" is pretty much unsearchable and the devs mark things as duplicate without providing a link to the issue it's apparently a duplicate of.
So is this fixed? Being worked on? Who the hell knows?
lpiljek
Aug 24, 2017 16:29
OK, so it's a duplicate. Where can I find the issue that this is a duplicate of?
This is so unprofessional... 2017.1 is completely unusable at this point.