Search Issue Tracker
Won't Fix
Votes
10
Found in
3.5.0f5
Issue ID
462740
Regression
No
When refresh web browser, the socket connection fails.
When refresh web browser, the socket connection is failed.
It means that the socket connection succeeds when open sample project in browser for the first time, but the socket connection fails after refreshing browser.
Mac only with Chrome or Safari.
Repro Steps:
1. Open the webplayer.html
2. Just check the log file
3. You will be able to see log messages like below
- Connected to the server
4. Refresh the browser
5. You will be able to see log messages like below
- Connected to the server
- Connection closed by the server
- Received from the server
6. Step 5 means the socket connection failed.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
janarjune
Nov 13, 2019 10:58
Got the problem solved using this link http://ccleaner-utility-software.strikingly.com/
alanrogger07
Jan 16, 2019 07:42
I have been checking for the solution of the same problem and came accross the site https://errorcode0x.com/chrome-crashing-windows-10-solved/ where I got a solution to fix the SMTP connection.
F.G.
Oct 03, 2014 13:59
I can reproduce this with unity3d 4.5.4 Safari Version 7.0.6 (9537.78.2)
Craig-Mesdag
Aug 29, 2014 22:51
Here's a quick script that is affected by this issue https://gist.github.com/CraigMesdag/cb57ad35cd7e21c47f32
mikesmallhorn
Jul 10, 2014 14:28
Bit more info: Bug can be repro'd in OSX 10.9.3 on browsers: Safari 7.0.4, Firefox 30.0, Chrome 35.0
mikesmallhorn
Jul 10, 2014 13:19
Repro'd in 4.5.2f1
johnnorthwood
Mar 21, 2014 05:05
I can repro this in 4.3.4f1