swiftshader | performance CPU-based implementation | Graphics library

I'm trying to create this lambda function in AWS using Amplify however when I try to launch the chromium the lambda function does not return any value and the function end up timing up:

"errorMessage": "2020-12-09T02:56:56.210Z 57402f8e-9fb2-4341-837d-bdf2ee6e9262 Task timed out after 25.57 seconds" I add the Layer as suggested by @James Shapiro, now I'm getting a URL return for the chromium but it still not launching it:

This is my function:

I am stuck with an issue which I dont seem to find any way to fix it.

I have created a batch file to launch the android emulator

I'm trying to have a docker container running on google cloud run, which is containing a simple nodejs app and google chromium headless to create a PDF from HTML source. Unfortunately, Google Cloud Run seems to have issues with thatever solution I try.

My Docker image(s) run perfectly locally and on other providers (i.E. Azure), but GCP just does not work.

What I try:

Basically building any docker image, installing node, npm, chromium, then running chromium --headless in the background. Then running the node app. The Node app is simply trying to connect to 127.0.0.1:9222 => that doesn't work on GCP, but anywhere else.

I tried with the official node images of docker hub I tried with an alpine image I tried with a debian image All of these run fine locally, but not on google cloud run.

Here's my latest test with a debian image:

I am using puppeteer in some back-end js within a react app.

The code is fairly simple in regards to the puppeteer components and it works when testing the app in a normal development script within yarn. The likely relevant code is fairly simple:

I have posted the same question over Unity's forum, but there hasn't been any answer and thus posting it here, too.

I have been trying to run a Unity WebGL build in headless mode (through puppeteer) while saving 'screenshots' of the game, but the camera rendering doesn't seem to be working. The resulting images are all black.

It works as expected when not in headless mode (but still WebGL). It also works properly in standalone builds (e.g., windows, mac), through -batchMode.

Here's the code in question:

Try use CEF from C++. Make simple project:

I have tried installing VS Code both via snap and via apt-get

In both cases code doesn't run on a Ubuntu 16.04 server where I use VNC to access the xfce GUI. When I run code --verbose from a terminal window I get

I'm trying to export an image rendered with WebGL on a linux server without a GPU. To do this I'm using headless Chrome however the exported image is black (example exported image, taking a screenshot of page shows its just canvas that is black). I was hoping for some help figuring out why this is happening.

To export the image I render the image into a canvas, export data via canvas.toDataURL('image/jpeg') and then post the data to the server. I'm using Pixi.js for rendering, if I use canvas renderer then everything works on the server; It's WebGL rendering thats not working. It's worth noting the WebGL render works fine in Chrome 63 on a Macbook.

To control Chrome I'm using Puppeteer. All I'm doing is opening a page, waiting a second, and then closing it again:

I seem to be loosing considerable precision toward the lower end of the color spectrum only when using hardware accelerated rendering on my Android emulator.

With hardware acceleration (ANGLE D3D11 or Desktop Native OpenGL):

Without hardware acceleration (SwiftShader):

The banding is clearly non linear and becomes quite obtrusive when trying to render smooth lighting.

I've set getWindow().setFormat(PixelFormat.RGBA_8888); and am using precision highp float; in my fragment shader.

This us using Android Studio 3.1.1, Windows 10, OpenGL ES 3.0.

*Edit: Here's a side by side with increased brightness and contrast