Memory leak when starting puppeteer with userDataDir in headlesss mode

[Zzombiee2361]

Bug description

Chrome process just use 50% CPU and keep eating memory. The qr event never fired.

Reproduction steps

Steps to reproduce the behavior:

1. Start client with userDataDir.
2. Open any process manager and watch as chrome process eating memory.
3. qr event also never fired.
   ...

Expected behavior

No memory leak and qr event gets fired.

Relevant code

const puppeteerPath = `./puppeteer_data/${id}`;
const client = new Client({
	puppeteer: {
		userDataDir: puppeteerPath,
		args: ['--no-sandbox']
	},
	session: sessionData,
	restartOnAuthFail: true,
});

Environment (please complete the following information):

WhatsApp

• Account type: Standard
• Device OS: Android

Library

• Browser: Chromium
• NodeJS version (node -v): v12.18.3
• npm or yarn version (npm -v): yarn v1.22.4
• whatsapp-web.js version: 1.7.0

Additional context

I'm trying to make multi session authentication. Either disabling headless or userDataDir fixes the issue, but I need both.

[pedroslopez]

This seems like an issue with puppeteer and the path specification. A very similar issue was reported here puppeteer/puppeteer#3453 and the fix was relating to path specification. Please take a look at that issue for more info.