Search Issue Tracker
Fixed in 5.1.0
Votes
11
Found in
5.0.1p1
Issue ID
689603
Regression
Yes
Chrome 42 doesn't run simple WebGL scene
-e: a very simple cube scene, chrome tab just spins for minutes at max cpu
-repro
--open attached project or just make a scene with a cube
--build for webgl
--run in FF
--notice it loads and you see the cube
--run in chrome 42
--NOTICE the tab stays at max cpu for minutes but nothing happens and you dont get to see your cube
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
AshtPidding
Apr 22, 2020 05:57
There are lots of tracker software that helps us to find out the place where a person can stay also it should have bugs in it. To resolve the bugs we use http://essaysoriginreview.com/review-on-bestessay-com/ it can provide us nine steps of analysis.
sirrus
Oct 26, 2015 19:19
Ack, disregard previous comment. (Wrong issue). Sorry about that.
sirrus
Oct 26, 2015 18:57
Sorry, but this isn't fixed in 5.2.1p3.
HybridMind
Apr 23, 2015 02:06
I was able to repro this in Unity 5.0.1f1 as well. Running into exact same issue w/ one of my other projects. Bad timing w/ Chrome killing the web player and WebGL Unity builds no longer working in Chrome too. :)