Skip to content
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

[Bug] Headless Chrome - Cannot read property 'blendFuncSeparate' of null #3004

Open
will-3ds opened this issue Jan 31, 2024 · 5 comments
Open
Labels
type: bug 🐞 Errors in functionality

Comments

@will-3ds
Copy link

Bug description

image
Got an error "Uncaught TypeError: Cannot read property 'blendFuncSeparate' of null" launching page with headless Chromium. The page with the renderer works fine with a classic Chrome/Chromium browser.
The command I use to run the headless is the following:
chromium --disable-gpu --headless --no-sandbox --ignore-certificate-errors --disable-web-security --profile-directory=Profile 1 --disable-features=DefaultPassthroughCommandDecoder --remote-debugging-address=0.0.0.0 --remote-debugging-port=9222 --verbose http://dev.local

Steps to reproduce

  • Launch page with a renderer in headless Chrome

Detailed Behavior

No response

Expected Behavior

Page should render correctly

Environment

  • vtk.js version: 24.19.2
  • Browsers: Chromium 90.0.4430.212 / Chrome 120.0.6099.225
  • OS: Windows 11
@will-3ds will-3ds added the type: bug 🐞 Errors in functionality label Jan 31, 2024
@daker
Copy link
Collaborator

daker commented Jan 31, 2024

Why are you disabling the gpu with --disable-gpu ?

@will-3ds
Copy link
Author

Omitting --disable-gpu outputs this error ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization

@daker
Copy link
Collaborator

daker commented Jan 31, 2024

can you try this and upload the result?
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --headless --ignore-gpu-blocklist --print-to-pdf=%userprofile%\Desktop\report-default.pdf chrome://gpu

Then this one
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --headless --ignore-gpu-blocklist --use-angle=swiftshader --print-to-pdf=%userprofile%\Desktop\report-vulkan.pdf chrome://gpu

You can try other backends with --use-angle to see which one works for you, ex : d3d11on12 or vulkan

@will-3ds
Copy link
Author

will-3ds commented Feb 1, 2024

Here are the reports:

@daker
Copy link
Collaborator

daker commented Feb 1, 2024

@will-3ds You don't have any hardware acceleration here and it seems you are running Chromium from within WSL2 on Windows 11, maybe try with --enable-gpu --use-gl=egl to see it works for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug 🐞 Errors in functionality
Projects
None yet
Development

No branches or pull requests

2 participants