[Bug]: WebP screenshots are always empty

[KevinVR]

Bug description

Steps to reproduce the problem

1. Use chrome-aws-lambda as a layer arn:aws:lambda:eu-west-1:764866452798:layer:chrome-aws-lambda:25
2. Navigate to a page await page.goto(url, {waitUntil: 'networkidle2'});
3. Take a screenshot result = await page.screenshot({ type: 'webp' });
4. The screenshot will be empty --> Buffer.byteLength(result) === 0
5. Looking at the actual buffer, it is really, really empty

This only happens with type: 'webp'. Using jpeg or png works perfectly. Somehow webp is always blank.

Browser

The browser is created in the usual way.

const chromium = require('chrome-aws-lambda');
const puppeteer = require('puppeteer-core');

await puppeteer.launch({
    args: chromium.args,
    defaultViewport: chromium.defaultViewport,
    executablePath: await chromium.executablePath,
    headless: chromium.headless,
    ignoreHTTPSErrors: true,
    dumpio: true
});

Environment

This happens on AWS-Lambda using the above layer ARN (chrome-aws-lambda)

However, I can reproduce it locally. using sam build sam local start-api the exact same issue occurs on Windows.

Puppeteer version

puppeteer-core 13.1.1

Node.js version

14.18.3

npm version

6.14.15

What operating system are you seeing the problem on?

Windows, AWS Lambda (Node 14)

Relevant log output

2022-01-23T16:25:03.914Z        09d98dd9-1ce1-44d7-99b6-2cefa32a1d6e    INFO    Make browser: 900.478ms
2022-01-23T16:25:03.944Z        09d98dd9-1ce1-44d7-99b6-2cefa32a1d6e    INFO    Make new page: 29.81ms
2022-01-23T16:25:03.946Z        09d98dd9-1ce1-44d7-99b6-2cefa32a1d6e    INFO    setViewport: 1.181ms
2022-01-23T16:25:05.139Z        09d98dd9-1ce1-44d7-99b6-2cefa32a1d6e    INFO    takesnap-goto: 1.193s
2022-01-23T16:25:05.139Z        09d98dd9-1ce1-44d7-99b6-2cefa32a1d6e    INFO    Generating image
2022-01-23T16:25:05.209Z        09d98dd9-1ce1-44d7-99b6-2cefa32a1d6e    INFO    Generated file length  0
2022-01-23T16:25:05.466Z        09d98dd9-1ce1-44d7-99b6-2cefa32a1d6e    INFO    S3 Upload: 256.519ms

[KevinVR]

Closing this, the reason is that chrome-aws-lambda and the layer arn are only compatible with Puppeteer 10.x right now.

An upgrade needs to happen on the https://github.com/alixaxel/chrome-aws-lambda project first. Opened ticket there: alixaxel/chrome-aws-lambda#254