Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0p1
Issue ID
986188
Regression
No
PhysicMaterial stays in memory after destroying its GameObject
To reproduce:
1. Open user's attached project
2. Open scene "Main"
3. Play the scene and pause it after a few seconds
4. Open Profiler, add Memory profiler and switch to detailed view
5. Take a memory sample, expand scene memory list
Expected result: The amount of "PhysicMaterial" is the same as "BoxColider"
Actual result: There are a lot more "PhysicsMaterial" than "BoxColider"
Reproduced with: 5.6.5p1, 2017.1.3f1, 2017.2.1p2, 2017.3.0p3, 2018.1.0b4
Notes:
- The amount of PhysicsMaterial is getting higher and higher even though the error
"Could not create Material. Maybe you have too many materials in your scene. Only 65535 are allowed." is displayed.
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
Add comment