Package: webext-foxyproxy
Version: 7.5.1+dfsg-1
Severity: normal

Hello,

occationally (I didn't find the trigger yet) a subprocess of firefox
occupies one complete cpu. There is no functional problem, all seems to
work just fine.

It was not clear to me what part of firefox is responsible for it, but
now I think it is foxyproxy. I started a new profile and the problem
didn't occur until I enabled foxyproxy. Today I looked in more detail
into the process' status before closing firefox (which cures the
problem):

According to strace the process (with pid 16443) does:

        read(8, "\372", 1)                      = 1
        recvmsg(17, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource 
temporarily unavailable)
        recvmsg(17, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource 
temporarily unavailable)
        poll([{fd=8, events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, 
events=POLLIN}], 3, 0) = 0 (Timeout)
        write(9, "\372", 1)                     = 1
        recvmsg(17, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource 
temporarily unavailable)
        recvmsg(17, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource 
temporarily unavailable)
        poll([{fd=8, events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, 
events=POLLIN}], 3, 0) = 1 ([{fd=8, revents=POLLIN}])

in a tight loop.

ls /proc/16443 contains:
lrwxrwxrwx   1 uwe  uwe  0 Apr 28 08:25 cwd -> '/proc/16444/fdinfo (deleted)'
lrwxrwxrwx   1 uwe  uwe  0 Apr 28 08:25 root -> '/proc/16444/fdinfo (deleted)'

and after I killed the process, normal web surfing is unaffected, and
foxyproxy doesn't work any more. (That is, the icon still appears in the
address bar and I can reconfigure foxyproxy, but when I access a site
that requires to pick a non-default proxy setting, firefox tries to
access it directly.)

I clicked a bit around in the developer console, looking for service
workers, but didn't find anything.
In the console there are a few messages:

        Promise resolved after context unloaded
        background.js:53
        Object { mode: "patterns", proxySettings: (2) […] }
         activeSettings in patterns mode background.js:176:13
        background.js: loaded proxy settings from storage. background.js:105:11
        Promise resolved after context unloaded
        vapi-background.js:1456
        The Components object is deprecated. It will soon be removed. 
regex.js:12:20

I have no idea how to further debug that.

Best regards
Uwe

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (700, 'testing-debug'), (700, 'stable-updates'), (700, 
'testing'), (700, 'stable'), (600, 'unstable'), (500, 'unstable-debug'), (500, 
'stable-debug'), (500, 'oldstable'), (499, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages webext-foxyproxy depends on:
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4

Versions of packages webext-foxyproxy recommends:
ii  firefox      88.0-1
ii  firefox-esr  78.10.0esr-1

webext-foxyproxy suggests no packages.

-- no debconf information

Reply via email to