Closed Bug 1561878 Opened 6 years ago Closed 5 years ago

Long startup times - connection reset by peer at ipc_channel_posix.cc

Categories

(Core :: Widget: Gtk, defect, P3)

69 Branch
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox67 --- ?
firefox68 --- ?
firefox69 --- affected

People

(Reporter: luis.pabon, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

  • Download firefox nightly from firefox's website
  • New profile

Actual results:

I get this on the console:

[Parent 5489, Gecko_IOThread] WARNING: pipe error (119): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

One of these per tab opened. When it's restoring my usual browsing session (which has a number of pinned tabs), startup takes ages as it seems to be doing that sequentially per tab in a blocking fashion.

I believe this to be related to its inability to open links as triggered from other apps. When I do that (for instance by clicking a link on the terminal), firefox pauses then shows an error dialog: "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system."

Expected results:

Firefox starts up fast. Links can be opened from other apps in an already running instance.

Firefox 69.0a1 (2019-06-26) (64-bit) - firefox's site tarfile (not nightly PPA)
Ubuntu 19.04

X11 or Wayland
New or old profile

Weird, I've seen that console error on close (bug 1550919). Weird to see it on start-up. Drew, any clue on what's going on or on how to debug this further?

Luis, is this behavior a regression for you? If so, can you please run mozregression to find a potential regressor? (https://mozilla.github.io/mozregression/)

Component: Untriaged → Widget: Gtk
Flags: needinfo?(luis.pabon)
Flags: needinfo?(adw)
Product: Firefox → Core

Did something happen recently to the directory containing your profile folder(s)? Did its permissions change, is it on a network drive, anything like that? If you create a new profile folder in another directory that's local to your machine and that you have permissions to access/write, does the problem still happen?

Flags: needinfo?(adw)

I will be testing this shortly with mozregression.

Drew, my disk setup is quite standard. An ext4 partition holds my home folder, including the moz profiles. This happens randomly also on a blank profile.

Flags: needinfo?(luis.pabon)

Just to point out I haven't been using the website's binaries until this week as I was trying to see if I could work around https://bugzilla.mozilla.org/show_bug.cgi?id=1555308 found while using firefox-trunk from mozilla's ubuntu ppa.

Priority: -- → P3

This has been fixed at some point 👍

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME

Works in FF81.

You need to log in before you can comment on or make changes to this bug.