Message-ID: <aaf0f04b-efbc-44c7-b5dd-a917c3fa59ad@vincentbentley.co.uk>
Date: Mon, 22 Jul 2024 20:50:36 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: firefox high cpu under sway
To: ~alpine/users@lists.alpinelinux.org
References: <87wmldec5c.fsf@ryzen.jonjfineman.com>
 <3eb0928e-9b4b-4932-ac8c-4bb3ee943443@schafweide.org>
 <87o76pdyo9.fsf@ryzen.jonjfineman.com>
Content-Language: en-GB
From: Vincent Bentley <vince@vincentbentley.co.uk>
Autocrypt: addr=vince@vincentbentley.co.uk; keydata=
 xsDNBGRC8UsBDADZ6S2vemKar4ZHeYTrC3sXtuNm/piHqptJIZasoeXmzfclYxSCAxLUncRP
 ftuLGxKTuPW5qKo1Jc7aIollltQutRufX7BLSyo1lKEFQFAEYN/Lfg8/170wt7aFYdAjGD8W
 eoFNTZFL0tfpVkrE2OYkExtTQ3z61nX1BQeb234lYRNj7e6LemsApX6S4uWKJtVRXd4+EIU3
 oeOEqQ8PdWroUWoUWRqr99fF+FGE81mOV3fbSTFNPkn4l60brL3V8cVMKqXSsUmT0UAuD91+
 iAupemrgjHWQQGbIKFHlv12z3hK6kMxl/iKJILR2Y2+xHB5neiIEAz3oBVyIIhuGDgI3MQ1W
 93KXkKUj2ofuKQMHW5ldpK6LKAmxx7fHLZaIGXF0Sdb1bh/GQRQD42Pw+7HXORD4ZdGIaVjP
 ahcxnI+aIe6ITIJ/MPSPi+h1pE2T/fshTEFqqqL7Zo5n0W4be34Mi7JjCf8Z68nz3s15Vjb+
 /FChhjix899TQVcmkZ6ELqkAEQEAAc0sVmluY2VudCBCZW50bGV5IDx2aW5jZUB2aW5jZW50
 YmVudGxleS5jby51az7CwQ0EEwEIADcWIQSUjAwAYn6lnn5mG7sqcTQrSN8i6gUCZELxSwUJ
 BaOagAIbAwQLCQgHBRUICQoLBRYCAwEAAAoJECpxNCtI3yLqUxAL/25NN+t2e296l7lJ9ov1
 1qT2sOvTkUqIdGLFXeF7GRLFpUqmqmTjIRVfS91T2hlfeKrCLza8MArIvVM3+1fcmvWl8aIl
 K8/QVG1YxuBpSDclzd05PAee+vQoAYTQR6Xm0wuHZrMY5gER5Ci+H7a45CfSqj7tE1Fz4v1U
 57x5nIfq7V6ObyosLj/iCu6dFlYRWHBdS+dOiQ3KO+5eNpLn2RkGQRaSOylucKk7mBi4kGUo
 n62LBQb//Pzc+PKhtQJl24znef5o93oNTUoM53dSCqlp4okJE9YJpO4i+CFs/AEbd3+b0xdk
 xb2bc2QVU4nIVrZd8B6RheuZ41C2+IZ8ReS/M7I7AL9QgkWisxV9nP+ghT3iKLt4nnGSn6y+
 ba2DkNitWXmozfLfJWDsyc1kPTLZDsi1LTlg+DXQcVfOLLaTX/fPhDeKIvWYNRR+qLwI6gGh
 cvlK/PMHeHgdy2eCfzRjHcuMEQN9D2cz6OqIkKTmxub/+mtxAJrERBjkGEza3c7AzQRkQvFM
 AQwAlQ43442bHElersx7MhtwGvManncSAVMjMlWP1ugKLpDEHPjDlf5I7eojLkpzh508qJQr
 1BkToESjeKxkPlkWXZbYlRUtQwVGb9m/yBuUvWqXPKBvv7LJQYoWATN6o4MR5smGjx39p1JY
 DeOqoGJ8Wh5cHe+fGGbDVr7xNKKAdgG7IdtYLmYel/dgf/a/xkKjZMf3rxmpF89JtymSL/Pz
 zdagv7unhq/WndGdvetZCLC4e3KF4+kaYrm61JfjSCDZRXjy2DKNw1zzMIHXX6bAgGC6X06F
 Tnz+gNk79lLQSMyNYSYf3KZ+TtRnuyb1NG2hlIa5AEC9GDrMNEuJJbIYJvIfLn1582TH8OQP
 d7sld8OhmqtT5JC0XBjssKoA5L/exwlZ0OGt6GwDvuyVX66b8qFWviT/ajPbpNDrLBvoYN4j
 rhQF4zZZCdcRsLqbU1EJIJXyQDs6c1poEqm0eBhbyMcQQj/S4fDzVDiMXEF5yQlBMWe2AOur
 23oXVhqUDA7xABEBAAHCwPwEGAEIACYWIQSUjAwAYn6lnn5mG7sqcTQrSN8i6gUCZELxTAUJ
 BaOagAIbDAAKCRAqcTQrSN8i6sz0DADUfqA9dxU74z5hEtCu0w6q1tDp/SlUv/tnFKlfMUzw
 8WOCPD5qW4X/IYtLtOrjxuFHAOBu269tTtfLmcMHMJsPH2A4GpeR/au1AwWr9AqVO2/jTDDZ
 jbGBmKxhioMxYs1tzUMfPh8T6Cq8vepbnEqjIs0ML+D9faVwD0J4ZNGK79vKqYfhAsBam4ID
 aacaYihGct1FEVL0HU9EfxJbPoLNgS+T+ShMlpeJj2FsZHoN4KP28L46qNzFoS+9G/fJqFdP
 D9tBPlbuOH14ouEomHBgfuV+/jtcUfs0ol7wXonEXoTPAHIgaYi9qeQGYEE1tDNEQOBZtMiy
 txBHQk+VPvplhBtQjf5o1EhlqAHrEHApFNoYGgPD/dFqyYZHRv4SYaN1LlTHlc+LWQSTJVyb
 YG2x05PjQM5LfqReJWSO6aKHKoIraQfxyVYqjab2GeflJkMenMbFVgfa5kxU+0JGQrKFQepr
 cIE/IOkKHvfbLjOLLVPwEp5WLkgpBbWXC8mYalg=
In-Reply-To: <87o76pdyo9.fsf@ryzen.jonjfineman.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

This is a just a suggestion for something to investigate...

How is your Firefox doing DNS resolution?
Is it via UDP to port 53 or
via TCP/UDP to port 53 (DNSSEC) or
via TLS on TCP port 853?

Are your resolvers capable of resolving how Firefox is configured?
Is a firewall blocking TCP port 853?
Is the DNS query result too big for UDP and TCP port 53 is not enabled 
for DNS?

-Vince-



On 22/07/2024 20:17, Jon Fineman wrote:
> 
> Bjoern Franke <bjo@schafweide.org> writes:
> 
>> Hi,
>>
>>
>>> I was wondering if anybody else was seeing this issue with Firefox and if
>>> anybody had any ideas how to fix it.
>>>
>>
>>
>> what does about:processes in Firefox show?
>>
>> Regards
>> Bjoern
> 
> 
> Well as I was taking a rather long time to figure out how to take a
> screen shoot in wayland firefox finally settled down. Not sure what
> would take 10 plus minutes to update. The only extensions I have are
> bitwarden, ublock origin, and disable html5 autoplay.
> 
> While the install is relatively new (~4 months), firefox had been
> working fine up until about two-three weeks ago.
> 
> A mystery I guess.
> 
> Thanks for your help.
> 
> Jon