I'm seeing this weird error in journalctl -b | egrep -i "keyring|pam" that I'd like to blame it on, but I don't know what's happening

mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope: Couldn't move process 2719 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope': No such process
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope: Failed to add PIDs to scope's control group: No such process
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope: Failed with result 'resources'.
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope: PID 2718 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope', skipping: No such process
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope: No PIDs left to attach to the scope's control group, refusing.
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope: Failed with result 'resources'.

any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which are by using different desktop managers/login managers, but nothing there did the trick. these (I believe) are the relevant settings I have set:

    services.gnome = {
      gnome-browser-connector.enable = true;
      gnome-keyring.enable = true;
      gnome-online-accounts.enable = true;
    };
    security.pam.services = {
      login.enableGnomeKeyring = true;
      gdm.enableGnomeKeyring = true;
      gdm-autologin.enableGnomeKeyring = true;
      gdm-fingerprint.enableGnomeKeyring = true;
      gdm-password.enableGnomeKeyring = true;
    };

any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which are by using different desktop managers/login managers, but nothing there did the trick. these (I believe) are the relevant settings I have set (pam ones are me trying to fix it to no avail) o:

    services.gnome = {
      gnome-browser-connector.enable = true;
      gnome-keyring.enable = true;
      gnome-online-accounts.enable = true;
    };
    security.pam.services = {
      login.enableGnomeKeyring = true;
      gdm.enableGnomeKeyring = true;
      gdm-autologin.enableGnomeKeyring = true;
      gdm-fingerprint.enableGnomeKeyring = true;
      gdm-password.enableGnomeKeyring = true;
    };

any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which almost all mention using different desktop managers/login managers, but nothing there did the trick. these (I believe) are the relevant settings I have set (pam ones are me trying to fix it to no avail) o:

    services.gnome = {
      gnome-browser-connector.enable = true;
      gnome-keyring.enable = true;
      gnome-online-accounts.enable = true;
    };
    security.pam.services = {
      login.enableGnomeKeyring = true;
      gdm.enableGnomeKeyring = true;
      gdm-autologin.enableGnomeKeyring = true;
      gdm-fingerprint.enableGnomeKeyring = true;
      gdm-password.enableGnomeKeyring = true;
    };

any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which almost all mention using different desktop managers/login managers, but nothing there did the trick, as I'm on gdm. these (I believe) are the relevant settings I have set (pam ones are me trying to fix it to no avail) o:

    services.gnome = {
      gnome-browser-connector.enable = true;
      gnome-keyring.enable = true;
      gnome-online-accounts.enable = true;
    };
    security.pam.services = {
      login.enableGnomeKeyring = true;
      gdm.enableGnomeKeyring = true;
      gdm-autologin.enableGnomeKeyring = true;
      gdm-fingerprint.enableGnomeKeyring = true;
      gdm-password.enableGnomeKeyring = true;
    };

In reply to @andrew15_5:matrix.org
I actually found some other extension that leaks memory. I hoped there would be only one.