[Bug]: missing trace for 2nd browser

[dimkin-eu]

Version

1.45.1

Steps to reproduce

test.describe("describe", () => {
    test("short spec", async ({page,browser}) => {
        await page.goto('https://playwright.dev/')
        const page2 = await (await browser.newContext()).newPage()
        await page2.goto('https://github.com/microsoft/playwright')
        await page.locator("bazinga").click()
        await page2.context().close()
    })
})

Expected behavior

• test fails
• trace contains all browsers from test

Actual behavior

• test fails ( this is fine )
• (it doesn't matter in which browser test fails) trace contains only trace from 'page' fixture

Additional context

1.44.1 was fine, 1.45.1 - fails

use: {
    // headless: false,
    ignoreHTTPSErrors: true,
    screenshot: "off",
    video: "off",
    trace: "on",
    contextOptions: {
        bypassCSP: true,
    },
},

Environment

System:
    OS: macOS 14.5
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 20.10 MB / 32.00 GB
  Binaries:
    Node: 20.13.1 - /usr/local/bin/node
    npm: 10.5.2 - /usr/local/bin/npm
    pnpm: 9.4.0 - /usr/local/bin/pnpm
  Languages:
    Bash: 3.2.57 - /bin/bash
  npmPackages:
    @playwright/test: 1.45.1 => 1.45.1

[dimkin-eu]

for sure related to #31541 and #31535

[mxschmitt]

Looks like already fixed on ToT - @dgozman should we cherry-pick?

[dimkin-eu]

hmm, there were case which sounds exactly like this , but looks like that tests didn't found ( one more ) regression :(
#23421

[mxschmitt]

I can verify this is fixed on @beta and should be fixed in v1.45.2 shortly.