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
Comments (4)
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
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. :)