Search Issue Tracker
Active
Under Consideration for 1.1.X
Votes
0
Found in [Package]
1.1.5
Issue ID
PROFB-316
Regression
No
"Texture Readback is not supported by WebGPU. Use AsyncGPUReadback Instead" error when capturing memory snapshot on a build using WebGPU graphics API
Steps to reproduce:
- Open attached project
- Open Build Profiles and switch to Web platform
- Set Client Browser Type to Safari (for me autoconnecting profiler to Chrome didn't always work)
- Enable Development Build and Autoconnect profiler
- Build and Run
- Once browser launches the build, open memory profiler window and capture new memory snapshot of the connected player
Actual results: New snapshot is created, "Texture Readback is not supported by WebGPU. Use AsyncGPUReadback Instead" is thrown to console, captured snapshot has no preview image
Expected results: Snapshot is created without any errors
Reproducible with versions: 1.1.5 (6000.1.0b10, 6000.2.0a6)
Reproduced on: Safari Version 18.3 (20620.2.4.11.5)
{}Could not test{}: Google Chrome Version 133.0.6943.142 (Official Build) (arm64)
Tested on (OS): Apple M3 Max, MacOS 15.3.1
Notes:
- Not reproducible with WebGL 2 Graphics API
- Can't tell if issue is only with the preview image or if snapshot itself is also wrong in some way. One thing that looks suspicious is that Allocated Memory Distribution for Graphics is 0MB. It was 14MB for me when building with WebGL 2 graphics API.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment