-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome headless lost WebGL support on MacOS #263
Comments
Getting Same Error. Can we expect the fix asap? |
Do you guys have a workaround? maybe patch-package? How did you solve this, I ran into this problem just now... |
Karma got deprecated since I opened this, so I ended up switching to the modern web test runner instead. It's working great! My PR looks huge, but that was mostly other cleanup; you can see the new config here. |
So you switched from karma to playwright? Can you link to the karma deprecation article? Or are you saying that only this plugin got deprecated? |
THANKS!! |
If you don't have a hard requirement for Chrome Headless, using regular Chrome will not have the WebGL issue. I just did that (granted it uses more memory, but at least I can run my unit tests without switching unit test frameworks or manually patching a file inside |
Starting with Chrome 109, WebGL contexts can no longer be created in my Karma tests, meaning I can no longer run my tests locally. It appears to be because Chrome no longer supports software rendering on Arm-based macbooks, so the work-around is to enable the GPU instead: https://bugs.chromium.org/p/chromium/issues/detail?id=1407025#c9
I tried adding the indicated flags, but it's still not working because the launcher is also adding
--disable-gpu
:karma-chrome-launcher/index.js
Line 172 in 5f70a76
Is there a reason the GPU should be disabled in headless mode? Is there a workaround for this, or can we remove this flag?
The text was updated successfully, but these errors were encountered: