Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.6
Issue ID
PROFB-337
Regression
No
"Unknown" memory increasing in the Memory Profiler when in Play mode
How to reproduce:
1. Open the attached “IN-99303” project
2. Enter Play mode
3. Unpause Play mode
4. Open the Memory Profiler
5. Click Capture in the Memory Profiler window
6. In the pop-up window select “Take Snapshot”
7. Wait for 5 minutes
8. Click Capture in the Memory Profiler window
9. In the pop-up window select “Take Snapshot”
10. In the Memory Profiler “Session” section scroll to “Session 4” and select the first snapshot
11. In the Memory Profiler window “The Main Component” toolbar select the “All Of Memory” tab
12. In “The Main Component” navigate to Unity Subsystems (Native → Unity Subsystems)
13. Select “Unknown” and observe the Allocated Size
14. In the Memory Profiler “Session” section scroll to “Session 4” and select the last snapshot
15. Repeat steps 1-13
Expected result: The first snapshot's “Allocated Size” value is the same as the last snapshot's “Allocated Size” value
Actual result: The last snapshot's “Allocated Size” value is ~300-500MB bigger than the first snapshot's “Allocated Size” value
Reproducible with: 1.1.0(2022.3.61f1, 6000.0.48f1, 6000.1.2f1, 6000.2.0a10), 1.1.6(2022.3.61f1, 6000.0.48f1, 6000.1.2f1, 6000.2.0a10)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Thank you for the bug report. We’ve taken a closer look at this and determined that the best way for us to deal with this is through a cross team initiative. To this end we are creating multiple internal tickets utilizing the reproduction projects from this and other bug reports for investigation and fix validation purposes.
Since this means voting on the bugs is no longer possible, nor is it possible to follow along on the status of the fix, we’ll move all of that into this Discussions thread (https://discussions.unity.com/t/unknown-memory-in-memory-profiler/920144/12). We’ll try our best to keep you updated on the status of this issue there.