Search Issue Tracker
Active
Votes
41
Found in
2021.3
2022.1
2022.2
2022.2.0a1
Issue ID
1388816
Regression
Yes
[WebGL][Chrome] "The message header is corrupted and for security reasons connection will be terminated." errors
How to reproduce:
1. Open the attached project
2. Open Test Runner window
3. Run Playmode tests on WebGL
Expected result: No issues
Actual result: "The message header is corrupted and for security reasons connection will be terminated." errors in the UI and browser console
Not reproducible after Build&Run
Reproducible with Google Chrome Version 96.0.4664.110
Not reproducible with Safari 15.2
Tested with MacBook Pro (16-inch, 2019), Big Sur 11.6.2
Reproducible: 2021.3.0f1, 2022.1.b1, 2022.2.0a1
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
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
kritikos
Nov 25, 2022 12:16
Tested on 2022.2.0b16 and still occurs! A fix would be highly appreciated. Being able to profile our webgl client is very important.
Jlsax
Sep 17, 2022 11:51
The message header is corrupted and for segurity reasons connection will be terminated
Me da este error y no se como solucionarlo.
Ayúdenme
jwtan_unity
Sep 06, 2022 04:33
Fix Versions:
2023.1.0a4
2022.2.0b3
2022.1.12f1
2021.3.8f1
m2yonnad
Aug 03, 2022 04:59
This is really frustrating not having profiling work. My app seems to be super slow on Chrome but not on Firefox - and not being able to profile it to figure out what's wrong is making me consider using a different game engine...
AldeRoberge
Jul 30, 2022 20:56
How to reproduce :
Unity 2021.3.5f1
WebGL Target
Autoconnect Profiler + Development Build
Open in Chrome
dimitroff
Jul 26, 2022 07:47
Can't believe that it has been reported half a year ago and this is still not fixed. :(
JegoBestaatal
Jul 22, 2022 08:16
Impossible to profile any WebGL stuff in 2021 LTS, and it gets tagged as low pain issue?
Dan_Dovi
Jul 19, 2022 08:29
Still occurring in Unity 2021.3.6f1
mathijs-mibo
Jun 02, 2022 06:14
We're also running into this issue after upgrading to 2021.3.1f1. Unable to profile our WebGL application using "Build and Run" with "Development Build" and "Autoconnect Profiler" switched on.
Would be really helpful to have a fix or workaround for this.
forcepusher
May 20, 2022 20:42
Again, this is not just about the Test Runner in 2022 - this is about the WebGL profiler in LTS 2021.
Profiler data sent to the Editor is corrupted, so it's impossible to profile our games.