From owner-freebsd-current@freebsd.org Mon Mar 25 14:24:23 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BC24156336F for ; Mon, 25 Mar 2019 14:24:23 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1FDA16E7D6 for ; Mon, 25 Mar 2019 14:24:21 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id 8QWKhNQg6Ldsa8QWLhyQV4; Mon, 25 Mar 2019 08:24:14 -0600 X-Authority-Analysis: v=2.3 cv=G9Zi7Os5 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=NTGMnVQrEZIA:10 a=pGLkceISAAAA:8 a=N6_MkC-iAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=UnuWRtxJqW8CloPxx0wA:9 a=7uutZGc21oGeu2Gq:21 a=4i-e-hNkBThBRr4u:21 a=QEXdDO2ut3YA:10 a=cD1l911K4WoA:10 a=xK3vmqMoOLAuYCf1I21x:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from android-68f84e02b5988183.esitwifi.local (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id A4E152FB; Mon, 25 Mar 2019 07:24:11 -0700 (PDT) Date: Mon, 25 Mar 2019 07:21:05 -0700 User-Agent: K-9 Mail for Android 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Long waits for Firefox and SeaMonkey to respond to links from other applications To: freebsd-current@freebsd.org, Kjell Tore Ullavik , Graham Perrin , FreeBSD CURRENT From: Cy Schubert Message-ID: X-CMAE-Envelope: MS4wfJhwmWaJed8swdCLdRIvcB5hsMfpG/94fDONXS0+EZbYvjvLjnegmNyaFyUGjpj7Fo4tGPu2cJr2H/FhLqJmHb+xFc0JC5//CjMUzYbGxOTZMh8Xigba GrZ8hYxg4RZH7PLnJ2XaTJwfArhxo1W46MQLR4Bcap247rDQqNadu4RTGKPjQzlion51OrZqBmjdv7P52xU2NXxRv05ldPA2QtJ9Vw6ROtG+dSDO+3DZdvIg o71plh4Gm1IRyxNWzMadVw== X-Rspamd-Queue-Id: 1FDA16E7D6 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-5.44 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; IP_SCORE(-2.25)[ip: (-5.86), ipnet: 64.59.128.0/20(-2.98), asn: 6327(-2.30), country: CA(-0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[9.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11, 233.154.66.70.zen.spamhaus.org : 127.0.0.11] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2019 14:24:23 -0000 On March 25, 2019 6:41:18 AM PDT, Kjell Tore Ullavik 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? >> >> 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 FreeBSD UNIX: Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E