playwright: Chromium crash on macos with PW 1.10.0[BUG]
Context:
-
Playwright Version: 1.10.0
-
Operating System: Macos 11.2.3
-
Node.js version: 14.16.0 and also on 14.15.4
-
Browser: Chromium
-
Extra: [any specific details about your environment]
System: OS: macOS 11.2.3 Memory: 13.24 GB / 64.00 GB Binaries: Node: 14.16.0 - ~/.nvm/versions/node/v14.16.0/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 6.14.11 - ~/.nvm/versions/node/v14.16.0/bin/npm Languages: Bash: 3.2.57 - /bin/bash npmPackages: playwright-chromium: ^1.10.0 => 1.10.0
Code Snippet Trying to create a snippet to reproduce.
Describe the bug
Running a test with cucumber and playwright on 1.10.0 in HEADLESS mode crashes with the error bellow. Works ok
- locally In headful.
- Locally when downgrading to 1.9.2
- on CI (Ubuntu 20)
page.waitForSelector: Protocol error (DOM.describeNode): Browser closed.
==================== Browser output: ====================
<launching> /Users/me/Library/Caches/ms-playwright/chromium-857950/chrome-mac/Chromium.app/Contents/MacOS/Chromium --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI,BlinkGenPropertyTrees,ImprovedCookieControls,SameSiteByDefaultCookies,LazyFrameLoading --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --user-data-dir=/var/folders/99/y2bb165n66q99tqwsv7bpt600000gn/T/playwright_chromiumdev_profile-vT6xKj --remote-debugging-pipe --headless --hide-scrollbars --mute-audio --blink-settings=primaryHoverType=2,availableHoverTypes=2,primaryPointerType=4,availablePointerTypes=4 --no-sandbox --use-fake-ui-for-media-stream --use-fake-device-for-media-stream --no-startup-window
<launched> pid=92589
[pid=92589][err] Received signal 11 SEGV_MAPERR 000000000008
[pid=92589][err] [0x00011571dce9]
[pid=92589][err] [0x0001156730d3]
[pid=92589][err] [0x00011571db11]
[pid=92589][err] [0x7fff20668d7d]
[pid=92589][err] [0x000000000000]
[pid=92589][err] [0x000113b39920]
[pid=92589][err] [0x000113b395ca]
[pid=92589][err] [0x000113b324ea]
[pid=92589][err] [0x000113b32100]
[pid=92589][err] [0x000113b31fe7]
[pid=92589][err] [0x0001156d7ec8]
[pid=92589][err] [0x0001156eb351]
[pid=92589][err] [0x0001156eb02a]
[pid=92589][err] [0x0001157312b7]
[pid=92589][err] [0x00011572b5e2]
[pid=92589][err] [0x000115730cef]
[pid=92589][err] [0x7fff2071ca0c]
[pid=92589][err] [0x7fff2071c974]
[pid=92589][err] [0x7fff2071c6ef]
[pid=92589][err] [0x7fff2071b121]
[pid=92589][err] [0x7fff2071a6ce]
[pid=92589][err] [0x7fff214a7fa1]
[pid=92589][err] [0x000115731801]
[pid=92589][err] [0x00011573089c]
[pid=92589][err] [0x0001156eb99b]
[pid=92589][err] [0x0001156b61fb]
[pid=92589][err] [0x0001157081b8]
[pid=92589][err] [0x00011570837b]
[pid=92589][err] [0x000115727be8]
[pid=92589][err] [0x7fff20624950]
[pid=92589][err] [0x7fff2062047b]
[pid=92589][err] [end of stack trace]
Add any other details about the problem here.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (9 by maintainers)
Here is a minimal repro:
Actually, I spoke too soon. I just got the same exact log on browser.close in Playwright 1.8. It looks like this crash has always been happening on macOS 11 on browser close. But it looks like it is happening mid-test for you. I filed a chromium bug that we’ll fix, but there seems to be more to the problem. I’ll keep digging.
Fix landed upstream as r869279
I can repro it, no feedback necessary atm. Looks specific to macOS 11 and fresh Chromium builds.
@aslushnikov - Running on chrome via channel or path is ok. running on canary via channel or path fails.
@Tallyb any chance you can share the code snippet to reproduce this?