You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We see that the frameAttached event for the main frame takes 5 seconds to arrive. This might be related to the slow-down to create a new process for the page.
We only see this happenning under the following circumstances:
in Firefox
with MacOS 14
on Github Actions
History: Firefox was timing out on macos-14 since the test bots were introduced: 4affcde
Reproduction:
Github Actions provide different architectures for the different size runners (details here and here):
macos-14 is aarch64 - ❌ has 5 seconds delay for each newPage
macos-14-large is x86-64 - ✅ works as intended
macos-14-xlarge is aarch64 - ❌ has 5 seconds delay for each newPage
Locally, on my macbook with MacOS-14 and aarch64 - ✅ works as intended.
This behavior reproduces with pptr-firefox with Firefox nightly, and webdriver-bidi with Firefox Stable
WebDriver script
const{ Builder }=require('selenium-webdriver');constfirefox=require('selenium-webdriver/firefox');(asyncfunctionexample(){letoptions=newfirefox.Options();// Enable BiDioptions.setPreference('remote.bidi.enabled',true);letdriver=awaitnewBuilder().forBrowser('firefox').setFirefoxOptions(options).build();try{// Navigate to a URLawaitdriver.get('about:blank');}finally{// Close the browserawaitdriver.quit();}})();
Puppeteer Firefox script
// make sure to run `npx puppeteer browsers install firefox` beforehandimportpptrfrom'puppeteer';constbrowser=awaitpptr.launch({product: 'firefox',});// Open a new pageconstpage=awaitbrowser.newPage();awaitpage.close();awaitbrowser.close();
The easiest reproduction so far is just running the headless screenshot:
Version
1.44.0
Steps to reproduce
Refer https://github.com/microsoft/playwright/actions/runs/8973892628
(another proof: https://github.com/canstand/playwright-go/actions/runs/8999400053/job/24721476663 )
Expected behavior
The test job takes similar time under different macos versions.
Actual behavior
Test job in macos-14(firefox) timeout.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: