Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
1
Found in
Issue ID
1234714
Regression
Yes
Native object references for some object types are always 0 in the memory profiler
Some native objects captured by the memory profiler always have 0 references, even though they should have some references. eg: Sprites not being referenced by SpriteRenderers or SpriteAtlases. This regression was brought in by the native connections overhaul which landed in the 2019.3.0b8.
Reproduction steps:
1. create a new scene
2. create a sprite atlas asset
3. use any default resource sprite or one of your choosing and have the atlas reference it
4. create a sprite object inside the scene
5. Install the memory profiler package
6. take a snapshot
7. open the snapshot
8. navigate to the native objects table from the tables dropdown
9. filter the type name by : "Sprite"
Expected:
The sprite native object should have at least 3 references. Clicking on the references will show connections to both the SpriteAtlas and it's SpriteRenderer
Actual:
The sprite native object has some number of references(1 or 0, depends if the managed shell is in memory or not). Clicking on the references will not show the SpriteAtlas and SpriteRenderer reference it
Reproduced on trunk 2020.2a6, no need to reproduce on 2020.1/19.3 as the code did not change in between.
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
- Scene View has an inverted Game View window when changing from Game View to Scene View on a specific project
- An error is thrown when one TreeView root element is dragged and held over a parent element but is dropped between the elements
- Text Object position shifts when selecting multiple Text Objects and expanding the Extra Settings in the Inspector
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a8
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b8
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.12f1