Search Issue Tracker
Active
Under Consideration for 6000.4.X
Votes
0
Found in
2022.2.21f1
6000.1.16f1
6000.2.3f1
6000.3.0b1
6000.4.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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit Button text is not rendered when the Button has fixed height with specific Icon font
- Unable to bind RenderTexture to the VisualElement's StyleBackground property
- SVG fails to import when 'stroke-miterlimit' is less than 1
- Test Runner fails to create a script in the active path when selecting a file as the active path
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
Add comment