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=2Ecom= > wrote: > > >On 24=2E03=2E2019 17=2E25, Graham Perrin wrote: >> When I open a web address in (for example) Thunderbird, there's a >wait=20 >> of around fifteen seconds before the web browser, already open,=20 >> handles the address=2E >> >> Affected browsers: >> >> - Firefox >> - SeaMonkey >> - Waterfox=2E >> >> Not affected: >> >> - New Moon (Pale Moon) =E2=80=93 the waiting period is a split-second >> - Chromium =E2=80=93 split-second >> - Falkon =E2=80=93 less than two seconds=2E >> >> Any ideas? >> >> <https://put=2Ere/player?id=3Db62zHf8k=2Em4v>; shows the waiting period = with > >> Konsole as the starting point, Firefox as the default web browser=2E >> >> I can't say exactly when the problem began, but it was long before=20 >> Firefox 66=2E >> >> ---- >> >> $ date ; uname -v >> Sun 24 Mar 2019 16:23:22 GMT >> FreeBSD 13=2E0-CURRENT r345330 GENERIC-NODEBUG >> $ pkg query '%o %v %R' firefox seamonkey waterfox >> www/firefox 66=2E0_3,1 poudriere >> www/seamonkey 2=2E49=2E4_24 FreeBSD >> www/waterfox 56=2E2=2E7=2E2 poudriere >> $ > >I have seen this as well=2E But not right now so can't investigate=2E >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=2E >Though that seems a bit weird=2E > > > >_______________________________________________ >freebsd-current@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd=2Eorg" The way to attack this problem is to run tcpdump on the interface while ru= nning DTrace against firefox or under truss -d=2E Simply running tcpdump wi= thout the other might give you enough information to at least make an educa= ted guess=2E Also, ff & friends are especially sensitive to load=2E If you're doing bui= ldworld -j while using ff, don't or give ff a higher priority=2E I've seen = it use multiple threads within multiple processes=2E Make sure you have lots of RAM=2E ff doesn't like to have any of it's work= ing set paged out=2E --=20 Pardon the typos and autocorrect, small keyboard in use=2E Cheers, Cy Schubert <Cy=2ESchubert@cschubert=2Ecom> FreeBSD UNIX: <cy@FreeBSD=2Eorg> Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A1CB0DD8-453B-406E-B413-EA66893E6FFF>