WebGL on HD 5500 works much worse than HD 4000
Reported by
ivan.kuc...@gmail.com,
Aug 1 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 Steps to reproduce the problem: 1. Go to www.Photopea.com , choose Demo: milk.sektch 2. Click in the middle and move the object around with a mouse. What is the expected behavior? On my previous laptop with Intel HD 4000, it worked at about 30 FPS. What went wrong? On my current laptop with Intel HD 5500, it runs at about 6 FPS. It feels like one of several frames takes much longer than other frames. I updated the drivers. Here is my about://gpu http://i.imgur.com/R3hH17c.png Did this work before? N/A Chrome version: 60.0.3112.78 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 26.0 r0 I bought a new laptop and expected a better performance of everything. I am sad, because it seems impossible to predict, how WebGL in Chrome will work on a laptop, that a person is going to buy. I am also disappointed, that many of my users may have an awful experience using my app, because of Chrome. My app does not have one drawElements call per frame with extra complex shaders, but it has dozens of small drawElements calls (with different shaders and uniforms) per frame. I also call copyTexSubImage2D a lot. I get much higher FPS on my new laptop in Firefox.
,
Aug 1 2017
,
Aug 1 2017
I just tried Chromium 56 Portable on Windows (on my new laptop) and it works equally bad. I also tried Chromium 56 on Ubuntu (on the same laptop) and it works significantly better (smoother). I think it is something between Chrome - Angle - GPU Drivers.
,
Aug 2 2017
,
Aug 9 2017
ivan.kuckir@ Thank you for the issue. Unable to reproduce the issue on Ubuntu 14.04, Windows 7 and Mac OS 10.12.6 using latest Stable 60.0.3112.90 and canary 62.0.3178.0 with the below steps 1. Opened the given url 2. Enabled the FPS meter from Dev tools. 3. Selected Demo: milk.sketch. Clicked on the object and moved it around with the mouse. 4. No issue is observed and FPS is recorded ~25-30. Please find the attached screen cast and confirm if anything missed here. Request you please try the issue on new profile without any extensions/flags and update the thread if the issue still exists.
,
Aug 9 2017
susanjuniab@ This bug occurs to me on Windows 7 with Chrome 60 and Intel HD 5500 as the GPU (used for WebGL). Do you have this GPU? Here is the screenshot of my FPS: http://i.imgur.com/cACV3uI.png . GPU Render is off, what does it mean?
,
Aug 9 2017
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 10 2017
ivan.kuckir@: please copy/paste (plaintext is fine) the entire contents of about:gpu. The screenshot in the description leaves off key information. Also: what exact brand and model of laptop is this? Here are about:gpu from a Razer Blade with Intel HD 620 running Windows 10, and a Lenovo ThinkPad with Intel HD 5500 running Windows 8.1. On both, performance of the test case is good. Can you upgrade to Windows 10?
,
Aug 10 2017
Here it is in HTML: http://www.ivank.net/veci/gpu.htm I have Lenovo Thinkpad e550 . I could not get used to Win10, so I downgraded to 7.
,
Aug 10 2017
We don't have this type of Broadwell (HD Graphics 5500) at hand. The only Broadwell desktop we have is Iris Pro Graphics 6200. Sorry that we may not help here.
,
Aug 10 2017
For some reason about:gpu from our Lenovo Thinkpad X250 was lost above. Re-attached. I also upgraded it to Windows 10 from 8.1, and installed Lenovo's latest drivers (Intel's won't install on this machine). ivan.kuckir@: the reason for the poor performance is that you're getting ANGLE's Direct3D 9 backend. I'm not sure why the D3D11 backend is failing to initialize on your machine, from your logs. It works fine on the machine we have here. Perhaps geofflang@ can suggest a way to diagnose what's going wrong. I suggest you reconsider your downgrade to Windows 10. Windows 7 isn't going to be receiving the latest driver upgrades forever.
,
Aug 10 2017
I was using the lastest drivers from Lenovo at first. The performance was bad, so I installed drivers directly from Intel, but it is still the same. The strange thing is, that Firefox performs much better (in the same environment in Windows 7). After looking into about:status, it seems like FF uses D3D 11. Chrome: ANGLE (Intel(R) HD Graphics 5500 Direct3D9Ex vs_3_0 ps_3_0) Firefox: ANGLE (Intel(R) HD Graphics 5500 Direct3D11 vs_5_0 ps_5_0) That is why I did not report it to Lenovo, or Intel, or Microsoft, but to you. Maybe it is because of some blacklist or something?
,
Aug 10 2017
Hard to say from the log why D3D11 isn't initializing. It could be missing Win7 platform updates, we require it for D3D11.
,
Aug 11 2017
Thanks geofflang@. Submitter, the reason this system is falling back to D3D9 is likely that the Platform Update for Windows 7 is missing: https://msdn.microsoft.com/en-us/library/windows/desktop/jj863687(v=vs.85).aspx This is a configuration error on the system. Closing as WontFix.
,
Aug 11 2017
Ok, thank you. I installed the update and Chrome uses DX11 now. The performance seems to be better now (I am getting 25 FPS). But is this Windows update really necessary? Firefox was capable of using DX11 without the update. Maybe there are many other users, who have bad WebGL performance for the similar reason and don't know, that it could be improved this way.
,
Aug 11 2017
The update is neccessary because it adds DXGI 1.2 which allows Chrome to create D3D11 devices from windows created in different processes while firefox only uses one process. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mailerd...@gmail.com
, Aug 1 2017