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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment