#1130952 firefox: startup time doubled due to glycin

Package:
firefox
Source:
firefox
Description:
Mozilla Firefox web browser
Submitter:
Johannes Stezenbach
Date:
2026-03-16 10:37:02 UTC
Severity:
normal
#1130952#5
Date:
2026-03-16 10:33:53 UTC
From:
To:
Dear Maintainer,

recently libgdk-pixbuf-2.0-0 was upgraded from 2.44.4+dfsg-1 ->
2.44.5+dfsg-3, with the new version enabling glycin image loaders
running in a bwrap sandbox with dbus IPC.
The results in a significant startup time regression.
Downgrading libgdk-pixbuf-2.0-0 to 2.44.4+dfsg-1 proves
that it is the culprit.

Since glycin seems to offer no way to trace/log which images
are loaded, I can only suspect that it could be related to a
large bookmark collection with associated icons.

extrace snippet with 2.44.5+dfsg-3:

    27220 firefox
      27224 /usr/lib/firefox/crashhelper 43 9 /tmp/firefox/ 11
      27234 /usr/lib/firefox/glxtest -f 18
      ...
      27296 /usr/lib/firefox/vaapitest -d /dev/dri/renderD128
      27313 /usr/lib/firefox/firefox -contentproc -ipcHandle 0 -signalPipe 1 -initialChannelId '{8e24e471-fe42-4dd0-8eb7-3c8a5f1dc2a4}' -parentPid 43 -greomni /usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appDir /usr/lib/firefox/browser 1 forkserver
      27319 bwrap --unshare-all --die-with-parent --chdir / --ro-bind /usr /usr --dev /dev --ro-bind-try /etc/ld.so.cache /etc/ld.so.cache --ro-bind-try /nix/store /nix/store --tmpfs /tmp-home --tmpfs /tmp-run --clearenv --setenv HOME /tmp-home --setenv XDG_RUNTIME_DIR /tmp-run --symlink /usr/lib32 /lib32 --symlink /usr/lib64 /lib64 --symlink /usr/lib /lib --symlink /usr/libx32 /libx32 --seccomp 56 /usr/bin/true
        27320 /usr/bin/true
      27322 bwrap --unshare-all --die-with-parent --chdir / --ro-bind /usr /usr --dev /dev --ro-bind-try /etc/ld.so.cache /etc/ld.so.cache --ro-bind-try /nix/store /nix/store --tmpfs /tmp-home --tmpfs /tmp-run --clearenv --setenv HOME /tmp-home --setenv XDG_RUNTIME_DIR /tmp-run --symlink /usr/lib32 /lib32 --symlink /usr/lib64 /lib64 --symlink /usr/lib /lib --symlink /usr/libx32 /libx32 --seccomp 57 /usr/libexec/glycin-loaders/2+/glycin-image-rs --dbus-fd 56
        27323 /usr/libexec/glycin-loaders/2+/glycin-image-rs --dbus-fd 56


I cannot decide if this should be reported upstream or to the glycin
developers, so I leave up to the maintainer to decide.