Search Issue Tracker
Fixed
Fixed in 6000.0.54f1, 6000.1.11f1, 6000.2.0b8, 6000.3.0a1
Votes
1
Found in
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99384
Regression
No
"_CameraTargetAttachmentB" unnecessarily Allocates Memory even when Post-Processing is disabled and Camera Stacking is not used
Reproduction steps:
1. Open the attached “IN-96545.zip” project
2. Open the “SampleScene”
3. Enter the Play mode
4. Open the Memory Profiler Window (Window > Analysis > Memory Profiler)
5. Click “Capture New Snapshot”
6. Open the captured Snapshot
7. In the Unity Objects tab search for the Allocated Memory of the “_CameraTargetAttachmentB”
Expected result: “_CameraTargetAttachmentB” does not allocate memory
Actual result: “_CameraTargetAttachmentB” allocates memory
Reproducible with: 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Couldn't test with: 2022.3.59f1 (Render Graph not compatible)
Reproducible on: Windows 11, macOS 15.3.1 (M1 Max)
Not reproducible on: no other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment