Apparently, there exists a preliminary fix for this issue.
-------- Forwarded Message --------
Subject: [Bug 1706594] 100% CPU usage on WebExtensions process
Date: Thu, 23 Sep 2021 18:22:36 +0000
*Comment # 32 <https://bugzilla.mozilla.org/show_bug.cgi?id=1706594#c32>
on Bug 1706594 <https://bugzilla.mozilla.org/show_bug.cgi?id=1706594>
from Luca Greco [:rpl] [:luca] [:lgreco] <mailto:lgr...@mozilla.com> at
2021-09-23 11:22:34 PDT *
I just looked to the debian bug report linked from comment 5
</show_bug.cgi?id=1706594#c5>
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986027) and then to
the content of the debian packages for one of the extension mentioned in
that bug and then I realized that the extension installed from these
debian packages are unpackaged and so they should be triggering the
exact same issue that I was able to trigger consistently using the STR
from comment 15 </show_bug.cgi?id=1706594#c15> (where ABP has to also be
loaded as unpacked to trigger the issue consistently).
e.g. the content of thewebext-private-badger one from
packages.ubuntu.com (debian.packages.org seems to don't be able to show
the list of files, but they should be packaged exactly in the same way
from this perspective):
* https://packages.ubuntu.com/hirsute/all/webext-privacy-badger/filelist
This confirms that the attached fix should also be covering the issue
experienced by debian/ubuntu users that are installing extensions from
deb packages instead of installing them from addons.mozilla.org (or by
installing the signed xpi non temporarily).
(I'm also clearing the previously assigned needinfos, I discussed the
proposed approach used in the current version of the attached patch with
Nika over Matrix and we will continue on phabricator).
