Search Issue Tracker
Fixed in 2021.3.33f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a14
Votes
4
Found in
2021.3.29f1
2022.3.7f1
2023.1.9f1
2023.2.0b4
2023.3.0a3
Issue ID
UUM-46008
Regression
No
RequestAsyncReadback triggers memory leaks when in Player
Reproduction steps:
1. Open the “RequestAsyncReadbackStripped” project
2. Ensure “Development Build” and “Autoconnect Profiler” are enabled in Build Settings
3. Build And Run
4. Navigate to the Memory module in Profiler
5. Click inside the graph and observe the used memory
Expected result: Used memory is below 1 GB
Actual result: Used memory quickly raises and stays around 2 GB
Reproduced in: 2021.3.29f1, 2022.3.7f1, 2023.1.9f1, 2023.2.0b4
Reproduced on: macOS 13.4.1 (Intel), Windows 10
Not reproduced on: No other environment tested
Notes:
1. Reproduced in StandaloneOSX and WebGL
2. Not reproduced in Play Mode
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment