[BUG] Hardware acceleration broken on certain GPUs

[saweiss]

Bug 描述
At least on my particular computer and OS (see specs below), I get the error message, "Laya3D init error,must support webGL!" in a pop-up shortly after I click Launch Game. I figured out that I could get past that error message if I opened the app with the following command in a terminal:

$ open -a Majsoul\ Plus --args --ignore-gpu-blacklist

So, by using Electron command line argument for ignoring the GPU blacklist, I was able to log into majsoul. However, when I went to spectate a game, I got a bunch of black bars over the screen (see image below). Turning off GPU acceleration in the settings did not help. In fact, even when ignoring the GPU blacklist, I got the webGL error message again. Any ideas what I can try to get majsoul-plus working on this particular computer? I got it working on another Mac, but I'm pretty sure it's because it has a non-blacklisted GPU.

如何重现
以下为重现步骤：

1. Use a Mac with a blacklisted GPU (see specs below for example).
2. Use the above command to open majsoul-plus without GPU blacklisting.
3. Trying launching a majsoul game with all combinations of the GPU related toggles in the majsoul settings pane ("Disable GPU acceleration" and "Enable GPU in-process"). The error message only appears when the "Disable GPU acceleration" button is toggled.

预期行为
I expect majsoul-plus to work comparably to how it runs in Chrome. In other words, no black bars and other bad renderings.

截图

客户端信息 (请完善以下信息):

• 操作系统: macOS Sierra v10.12.6 on MacBook Pro (13-inch, Early 2011)
• 系统架构: x86
• 版本号: majsoul-plus v1.11.1 and v1.11.2

备注
For what it's worth, I get the same black bar overlay when I try to run majsoul in Firefox. For some reason, even though hardware acceleration is enabled in both Chrome and Firefox on my computer, majsoul plays fine in Chrome, but not Firefox.

[iamapig120]

Could you tell me your Chrome version ? Thank you.

[saweiss]

I am using Chrome Version 73.0.3683.86 (Official Build) (64-bit). Thanks!

[iamapig120]

I am using Chrome Version 73.0.3683.86 (Official Build) (64-bit). Thanks!

Got it

[saweiss]

Perhaps it would help to have a print-out of my chrome://gpu/ page:
chrome---gpu.pdf

[Yesterday17]

Does this issue exist in the latest release?