Search Issue Tracker
In Progress
Fix In Review for 6000.4.0a5
Fixed in 6000.5.0a1
In Progress in 6000.5.X
Votes
0
Found in
6000.4.0a1
6000.5.0a1
Issue ID
UUM-117114
Regression
No
[FrameDebugger][WebGL] Disable the possibility in Frame Debugger to allow receiving data from the WebGL build
Steps to reproduce:
- Download attached project and open in Unity.
- Make sure Run In Background is enabled in the Player Settings.
- Switch the module to WebGL in the Build Settings.
- Enable Development Build, Atoconnect Profiler and Deep Profiling Support in Build Settings.
- Build and Run the project.
- Once the project is built and launched, open the Frame Debugger >> Window >> Analysis >> Frame Debugger.
- It shows that Autoconnect is the connection source.
- Press the Enable button.
Observe: No data will be displayed. Enable button is active and the user can trigger it.
Actual results: No data is displayed when using WebGL build. Enable button is interactive.
Expected results: Frame Debugger should not allow WebGL build to be captured. Enable button should be disabled. Warning in the Console should be printed that WebGL platform is not supported.
Reproducible with versions:
2022.2.21f1, 6000.1.16f1, 6000.2.3f1, 6000.3.0b1, 6000.4.0a1
Tested on (OS):
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS: 15.5
Windows 11 Pro; Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (36 CPUs), ~3.0GHz; NVIDIA GeForce RTX 3080; 128 GB RAM
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.5.0a1):
Verified with:
6000.5.0a1_0136d73297
Device under testing:
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS: 15.5