Date: Mon, 25 Mar 2019 07:21:05 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: freebsd-current@freebsd.org, Kjell Tore Ullavik <ktullavik@gmail.com>, Graham Perrin <grahamperrin@gmail.com>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Long waits for Firefox and SeaMonkey to respond to links from other applications Message-ID: <A1CB0DD8-453B-406E-B413-EA66893E6FFF@cschubert.com> In-Reply-To: <2d69326a-a446-517f-32d0-bd62e7aeaf2b@gmail.com> References: <63ce1a37-fffb-696f-5e56-492cc81c03b0@gmail.com> <2d69326a-a446-517f-32d0-bd62e7aeaf2b@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On March 25, 2019 6:41:18 AM PDT, Kjell Tore Ullavik <ktullavik@gmail.com> wrote: > > >On 24.03.2019 17.25, Graham Perrin wrote: >> When I open a web address in (for example) Thunderbird, there's a >wait >> of around fifteen seconds before the web browser, already open, >> handles the address. >> >> Affected browsers: >> >> - Firefox >> - SeaMonkey >> - Waterfox. >> >> Not affected: >> >> - New Moon (Pale Moon) – the waiting period is a split-second >> - Chromium – split-second >> - Falkon – less than two seconds. >> >> Any ideas? >> >> <https://put.re/player?id=b62zHf8k.m4v>; shows the waiting period with > >> Konsole as the starting point, Firefox as the default web browser. >> >> I can't say exactly when the problem began, but it was long before >> Firefox 66. >> >> ---- >> >> $ date ; uname -v >> Sun 24 Mar 2019 16:23:22 GMT >> FreeBSD 13.0-CURRENT r345330 GENERIC-NODEBUG >> $ pkg query '%o %v %R' firefox seamonkey waterfox >> www/firefox 66.0_3,1 poudriere >> www/seamonkey 2.49.4_24 FreeBSD >> www/waterfox 56.2.7.2 poudriere >> $ > >I have seen this as well. But not right now so can't investigate. >Could it be a dbus problem? > >I also have a vague and incomplete memory of fixing a similar >problem a long time ago by filling out my /etc/hosts. >Though that seems a bit weird. > > > >_______________________________________________ >freebsd-current@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd.org" The way to attack this problem is to run tcpdump on the interface while running DTrace against firefox or under truss -d. Simply running tcpdump without the other might give you enough information to at least make an educated guess. Also, ff & friends are especially sensitive to load. If you're doing buildworld -j while using ff, don't or give ff a higher priority. I've seen it use multiple threads within multiple processes. Make sure you have lots of RAM. ff doesn't like to have any of it's working set paged out. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A1CB0DD8-453B-406E-B413-EA66893E6FFF>