Context:

System:

• OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
• Memory: 11.14 GB / 27.24 GB
• Container: Yes (reported by npx envinfo, even outside of snap)

Binaries:

• Node: 18.13.0 - /usr/bin/node
• Yarn: 1.22.19 - /usr/bin/yarn
• npm: 8.19.3 - /usr/bin/npm

Languages:

• Bash: 5.1.16 - /usr/bin/bash

Describe the bug

Slightly odd problem here (and it may be out of Playwright's control).

When I run Playwright v1.30.0 inside the terminal in the snap version of WebStorm (e.g. version 2022.3.2), it is unable to launch Firefox with varying symptoms (depending on headless vs headed).

When running headless

Playwright hangs indefinitely. After pressing Ctrl-C, it prints:

    Test was interrupted.

    Fixture "browser" timeout of 0ms exceeded.

When running headed

There are a few errors. First, this:

Followed by:

[WebServer] (node:342129) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
(Use `node --trace-deprecation ...` to show where the warning was created)
  1) [firefox] › example.spec.ts:4:7 › @setA › test a ==============================================

    browserContext.newPage: Protocol error (Browser.newPage): Unexpected number of tabs in the new window: 2 newPage@chrome://juggler/content/TargetRegistry.js:317:13

The extra tab is a Firefox privacy notice (https://www.mozilla.org/en-US/privacy/firefox/). The browser looks like this:

It says it is using the profile /tmp/playwright_firefoxdev_profile-pkwZ9l (which is presumably correct).

I see various differences in the Firefox configuration that is used in this scenario. For example, with v1.30.0 inside snap:

  "processes": {
    "remoteTypes": {
      "extension": 1,
      "web": 1,
      "webIsolated": 1,
      "privilegedabout": 1,
      "prealloc": 3,
      "socket": 1
    },
    "maxWebContentProcesses": 8
  },

v1.29.2 inside snap:

  "processes": {
    "remoteTypes": {
      "extension": 1,
      "web": 1,
      "socket": 1
    },
    "maxWebContentProcesses": 60000
  },

When there is no problem

There is no problem with Playwright v1.29.2 inside WebStorm snap. There is also no problem when running Playwright v1.30.0 outside of WebStorm snap. And there is also no problem if I run Playwright inside the official container image inside WebStorm.

Repro

The specific project doesn't seem to matter, but I pushed a simple example here: https://github.com/jpveooys/playwright-repro/tree/firefox-1-30-0 (where playwright test --project firefox can be run).