Search Issue Tracker
Fixed
Fixed in 6000.0.63f1
Votes
0
Found in
6000.0.61f1
Issue ID
UUM-125744
Regression
Yes
WebGPU performance regression
Steps to reproduce:
- Build a project in Development Mode
- In the Chrome DevTools, select Source and select the framework.js file
- Search for wgpuLinkParentAndChild.
Actual results:
wgpuLinkParentAndChild has the code
parent.derivedObjects = {};
which is the source of the performance issue in Chrome.
Expected results:
wgpuLinkParentAndChild has the code
parent.derivedObjects = new Map();
Reproducible with versions:
6000.0.59f
Not reproducible with versions:
6000.0.27f.
Can’t test with versions:
Tested on (OS):
Notes:
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note (fix version 6000.0.63f1):
Fix WebGPU performance regression