In https://gitweb.gentoo.org/repo/gentoo.git/commit/www-client/firefox?id=98acf466e0f73a4d46f34e495344ac25901cf61f, the patchset was updated to firefox-101-patches-05j.tar.xz, but there was no revbump. Within the patchset, there is a critical fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1773968. A build without the fix would suffer from crazy memory leak, e.g. firefox can occupy more than 50GB of memory after moving around in google.com/maps for about a minute or so.
:\ I thought about it real hard whether to revbump or not, but 1) I'm sure most people just update their systems being unaware vaapi is now even available, 2) I couldn't tell who are affected by the bug you linked, it didn't seem _too_ widespread. So yeah, if you had problems the patch is now available, if you didn't have problems, you'll waste x amount of time... But maybe I could get away with it by saying such is life when running ~unstable. Anyway those VAAPI patches just keep on piling up even after the most recent patchset so for the next possible patchset update, I should revbump. https://bugzilla.mozilla.org/show_bug.cgi?id=1610199 (And in ~9 days we'll get 102 anyway)
*** Bug 852938 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=55dab4ff34008b06adc25b088d8abfc5c199606a commit 55dab4ff34008b06adc25b088d8abfc5c199606a Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2022-06-17 19:25:30 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2022-06-19 08:34:23 +0000 www-client/firefox: update wayland and vaapi patches - prepare wayland-only ebuild to be unmasked. Bug: https://bugs.gentoo.org/852299 Bug: https://bugs.gentoo.org/848858 Signed-off-by: Joonas Niilola <juippis@gentoo.org> www-client/firefox/Manifest | 1 + www-client/firefox/firefox-101.0.1-r11.ebuild | 1293 +++++++++++++++++++++++++ 2 files changed, 1294 insertions(+)
