Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REGRESSION]: NS_ERROR_FILE_ALREADY_EXISTS with Firefox sporadically #3337

Closed
pavanreddy61 opened this issue Aug 7, 2020 · 7 comments
Closed
Assignees

Comments

@pavanreddy61
Copy link

pavanreddy61 commented Aug 7, 2020

Context:

  • GOOD Playwright Version: 1.1.1
  • BAD Playwright Version: 1.2.1 and 1.2.0
  • Operating System: Linux or Debian
  • Extra: Using docker build similar to docker bionic in docs folder
 TimeoutError: Timeout 120000ms exceeded during browserType.launch.
21:23:47      ================= browserType.launch logs =================
21:23:47      [browser] <launching> /home/pwuser/.cache/ms-playwright/firefox-1122/firefox/firefox -no-remote -headless -profile /tmp/playwright_firefoxdev_profile-87DLpD -juggler 0 -silent
21:23:47      [browser] <launched> pid=656
21:23:47      [browser] *** You are running in headless mode.
21:23:47      [browser] JavaScript error: playwright.cfg, line 265: NS_ERROR_FILE_ALREADY_EXISTS: Component returned failure code: 0x80520008 (NS_ERROR_FILE_ALREADY_EXISTS) [nsICrashReporter.submitReports]

Describe the bug
The bug is coming up sporadically and only firefox shows that error. ReRuns are mostly successful, so not sure if i am doing something wrong. But before in 1.1.1 version we didnt see this issue anytime from last 1 month

Add any other details about the problem here.
Screenshot 2020-08-07 at 9 11 33 AM

Thanks and let me know if am doing something wrong here, webkit and chrome works fine and firefox also gets this error 1 out of 5 times now

@dgozman
Copy link
Contributor

dgozman commented Nov 24, 2020

@pavanreddy61 Sorry for the late response! Does this still happen with the new Playwright version like 1.6?

@pavelfeldman
Copy link
Member

We seem to be late to collect feedback from the customer. Could you check it against 1.6 and file a bug linking this one if it still persists?

@Prior99
Copy link

Prior99 commented Feb 2, 2021

Hi, sorry to necrobump this, but I am encountering this issue in playwright 1.8.0 when multiple firefox instances are spawned in parallel on a kubernetes pod:

      Failed to start browser "firefox": browserType.launch: Timeout 30000ms exceeded.
      =========================== logs ===========================
      <launching> /root/.cache/ms-playwright/firefox-1225/firefox/firefox -no-remote -headless -profile /tmp/playwright_firefoxdev_profile-OLSaD7 -juggler-pipe -silent
      <launched> pid=1332
      [err] *** You are running in headless mode.
      [err] JavaScript error: playwright.cfg, line 272: NS_ERROR_FILE_ALREADY_EXISTS: Component returned failure code: 0x80520008 (NS_ERROR_FILE_ALREADY_EXISTS) [nsICrashReporter.submitReports]
      [out] [GFX1-]: glxtest: libpci missing
      [out] [GFX1-]: glxtest: Unable to open a connection to the X server
      [out] [GFX1-]: glxtest: libEGL initialize failed
      [out] [GFX1-]: No GPUs detected via PCI
      ============================================================
      Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.

@dgozman dgozman added P2-bug and removed triaging labels Feb 3, 2021
@dgozman dgozman reopened this Feb 3, 2021
@dgozman dgozman added the v1.9 label Feb 3, 2021
@dgozman dgozman assigned JoelEinbinder and unassigned aslushnikov Feb 4, 2021
@aslushnikov
Copy link
Collaborator

aslushnikov commented Feb 22, 2021

This should be fixed with #5514 that disables crashrerpoter altogether in our builds. The fix will be released in v1.9.0

@skyuplam
Copy link

=========================== logs ===========================
<launching> /ms-playwright/firefox-1238/firefox/firefox -no-remote -headless -profile /tmp/playwright_firefoxdev_profile-NzVLBt -juggler-pipe -silent
<launched> pid=199
[pid=199][err] *** You are running in headless mode.
[pid=199][out] Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.341014) [GFX1-]: glxtest: libpci missing
[pid=199][out] Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.341014) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.341124) [GFX1-]: glxtest: libEGL initialize failed
[pid=199][out] Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.341014) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.341124) |[2][GFX1-]: glxtest: Unable to open a connection to the X server (t=0.341144) [GFX1-]: glxtest: Unable to open a connection to the X server
[pid=199][out] Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.341014) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.341124) |[2][GFX1-]: glxtest: Unable to open a connection to the X server (t=0.341144) |[3][GFX1-]: glxtest: libEGL initialize failed (t=0.341156) [GFX1-]: glxtest: libEGL initialize failed
[pid=199][out] Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.341014) |[1][GFX1-]: glxtest: libEGL initialize failed (t=0.341124) |[2][GFX1-]: glxtest: Unable to open a connection to the X server (t=0.341144) |[3][GFX1-]: glxtest: libEGL initialize failed (t=0.341156) |[4][GFX1-]: No GPUs detected via PCI (t=0.341176) [GFX1-]: No GPUs detected via PCI
[pid=199][out] 
[pid=199][out] Juggler listening to the pipe
[pid=199][out] console.warn: SearchSettings: "get: No settings file exists, new profile?" (new Error("", "(unknown module)"))
[pid=199][err] 
[pid=199][err] (/ms-playwright/firefox-1238/firefox/firefox:248): GLib-GObject-CRITICAL **: 08:08:37.070: g_object_set: assertion 'G_IS_OBJECT (object)' failed

We having the same issue with playwright@v1.10.0 running under Ubunto 20 using mcr.microsoft.com/playwright:focal

@mxschmitt
Copy link
Member

@skyuplam is it reproducible for you? If so a minimal reproducible would help a lot to fix this bug.

@skyuplam
Copy link

skyuplam commented Mar 30, 2021

Hi @mxschmitt , thanks for your response. We have managed to fix the issue via setting higher timeout value. Launching Firefox headless mode in Linux is slower than the previous version we used. Anyways, thank for your attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants