Search Issue Tracker
Fixed in 2022.3.52f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.X, 7000.0.0a8, future release
Votes
6
Found in
2022.3.41f1
6000.0.14f1
6000.1.0a2
Issue ID
UUM-77354
Regression
Yes
Memory leak in Texture2D.CreateExternalTexture when using D3D11 platform
Reproduction steps:
1. Open the “BugRepro” project
2. Open the “Assets/Scenes/SampleScene” Scene
3. Enter Play Mode
4. In the Memory Profiler window (Window > Analysis > Memory Profiler), capture a memory snapshot
5. Wait 10 minutes
6. Capture a second memory snapshot
7. Compare both snapshots
Expected: the memory usage between the snapshots remains roughly the same
Actual result: the second snapshot has additional 10GB of untracked memory
Reproducible with: 2022.1.0a13, 2022.3.41f1, 6000.0.14f1
Not reproducible with: 2021.3.42f1, 2022.1.0a12
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
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 ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
- "Too many sprite tiles on Image" error is spammed in the Console when editing Pixels Per Unit Multiplier on a Tiled Image Type for Scroll View
Add comment