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

Unable to Render WebGL Websites #80

Open
felixpitterling opened this issue Jan 26, 2025 · 0 comments
Open

Unable to Render WebGL Websites #80

felixpitterling opened this issue Jan 26, 2025 · 0 comments

Comments

@felixpitterling
Copy link

Hi there,

I’m trying to render WebGL-based websites using playwright-aws-lambda and came across a relevant discussion in the serverless-chrome repository. In this thread, there were multiple comments discussing how to enable WebGL rendering in serverless environments, with either SwiftShader or OSMesa being required.

In particular, I looked into this comment by @apalchys], where they provided a working implementation (including a demo) for WebGL rendering. The implementation involved:

  • The rendering binary placed in the same directory as the Chromium binary
  • Specific Chromium launch arguments:
    • --use-gl=osmesa
    • --enable-webgl
    • --ignore-gpu-blacklist
    • --homedir=/tmp
    • --single-process
    • --data-path=/tmp/data-path
    • --disk-cache-dir=/tmp/cache-dir

I attempted to use this exact setup with playwright-aws-lambda, hoping the presence of the swiftshader.tar.br file would allow me to achieve the same results. However, I encountered the following error:
browserContext.newPage: Target page, context or browser has been closed.

I only have surface-level knowledge of the issue and would appreciate any insight.

Thanks in advance for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant