Our game has recently stopped working on Edge browsers. We are running the game as a Facebook canvas game and it works great on Chrome and Safari. Edge used to work great, but on recent builds the game just freezes after a few seconds. There is no apparent error on the console. I tried increasing the WebGL memory, but it did not seem to change anything. On chrome I can run with the default 256Mb memory size without any problem. Anyone encountered similar problem with WebGL on Edge?
Hi Marco The Edge build we are seeing this: 40.15063.674.0 (HTML version 15.15063) We are using Unity version 2017.1.1f1 What do you mean by WebGL content? Thanks
I am experiencing this with my current project, haven't tried a different one.. The thing is that it works great on Chrome and Safari and it used to work great on Edge. Are you aware of any known problems with Edge? maybe something was changed in the latest versions?
Hi, I have same probrem. WebGL build freeze after a few seconds on Microsoft Edge. (It works fine on Firefox and Chrome) Unity version 5.3.8f1 Edge version 40.15063.674.0 (HTML version 15.15063)
Hi, Seeing similar problem with 5.4.6 Unity build and EdgeHTML 15.15063. - If Edge debugger is connected it loads super slowly but there's a message saying "asm.js disabled because debugger is on" - If debugger is disconnected, console is logging out of memory error and if freezes on (presumably) asm.js parse stage
On my project the freeze happens after the asm.js parse (I think) since the game starts ok. The memory profiler and developer tools are lousy on Edge and I cannot see any error. Like others here, my game works perfectly on Chrome, Firefox and Safari. It used to work great on Edge too, but something has changed. Unity version 2017.1.1f1
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/14829252/ We found that an older version of Edge was running our project fine, given that all kinds of versions of Unity are failing it seems it's an Edge issue. Unless, the less likely scenario, that Edge fixed something that allowed Unity WebGL run uninterrupted.
I tried to reproduce this here myself, but I could only get Edge fail at the same memory size the other browsers fail. A repro project that triggers the issue for you guys would be really helpful if you can send it via a bug report. Thanks!
We've tried many webgl and unity webgl projects on Edge and they seem to work fine. But there is a number of people facing the same issue which is signaling something quite specific. Maybe it's a specific asset that is causing this crash, like PostProcessingStack crashes the game few seconds in it (but that's a different subject). However, no luck finding what causes this particular issue to appear. We can't give a reproduction project yet as we don't know what causes it and sharing a company project is not an option. Can't confirm on the WebAssembly but happens with asm.js builds.
Have some reproduction steps. The issue happens in a different stage, but is throwing the same error and WebGL is not loading at all after page reload on the same tab which also happens when our project freezes. Unity 2017.1f1 1. Start new project 2. Import Standard assets 3. Build "CharacterThirdPerson" scene from "SampleScenes" folder for WebGL (default settings) 4. Walk around in the scene, bump into red square, try jumping on them until game freezes. Not very concise reproduction and will be working on cleaner steps, but that's what we have so far.
We're also having a similar (same?) issue. It seems we got a Windows update (in Windows 10) this morning which also made some updates to Edge and after that our application usually doesn't even load anymore in Edge while it still works fine in Chrome and Firefox. It used to work fine in Edge as well. At one point it seems it started when the F12 console was open. We're using Unity 5.5.4p4 Microsoft Edge 40.15063.674.0 Here's a link to our application you can test with: https://ds.spark-vision.com/blueprint_online/?sboc=SparkVision
Please feel free to use http://webgl.sumdog.com/ to reproduce. Microsoft Edge 40.15063.674.0 we almost immediately get SCRIPT7: Out of memory Microsoft Edge 40.15063.0.0 it works fine. Microsoft Edge 41.16299.15.0 works fine as well Works fine on chrome and firefox. Please note, on a version that works, after the loading screen you will go to a black screen, click 4 times near the centre to see something.
Hi, We received a response from the edge team about the issue we have been seeing https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/14829252/ They have fixed in edge 16, which you get in the fall creators update
We are seeing a different behavior on the 41.16299 Edge update with our game. After the game loads, the browser refreshes itself.. it seems that instead of freezing, the browser just tries to overcome the problem by refreshing the page. Anyone else got this?
One of my collegues got this behaviour with our application also. Now I am seeing the same when I tested in a VM I just updated to new Fall Creators version of Windows with Edge version 41.16299.15.0. It can actually start if I have the Edge F12 console open. I think the asm.js AOT compilation is disabled then so it might be related to that.
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/14829252/ Should be fixed in Edge 16
I found that using WebAssembly seems to solve the issue on Edge 41. This will not work on older Edge versions though