Xorg/lightdm strange memory leak?

Technical Issues & Assistance
1

I have no idea what is going on here. After reboot, everything seems fine for a while, I suspect the problem starts after I use some electron app, but I don’t understand the connection with xorg/lightdm and this high memory usage:

2023-02-15_06-06
2023-02-15_06-061056×266 44.3 KB

aaaa
aaaa1397×250 86.5 KB

2 Likes
2

I came home to this and I don’t like it at all, but as soon as I started using the PC the CPU usage dropped.

image
image1086×607 69.5 KB

1 Like
3

You could try sudo systemctl status lightdm and take a look for any errors @drlobes.

3 Likes
4 
~►sudo systemctl status lightdm                                                                                                                                                                     25315.038s 15:46
[sudo] password for x:
● lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-02-05 04:56:38 EET; 1 week 3 days ago
       Docs: man:lightdm(1)
   Main PID: 627 (lightdm)
      Tasks: 14 (limit: 38404)
     Memory: 4.5G
        CPU: 2d 3h 46min 13.260s
     CGroup: /system.slice/lightdm.service
             ├─   627 /usr/bin/lightdm
             └─486158 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

Feb 05 04:56:42 archlabs lightdm[767]: gkr-pam: unable to locate daemon control file
Feb 05 04:56:42 archlabs lightdm[767]: gkr-pam: stashed password to try later in open session
Feb 05 04:56:42 archlabs lightdm[767]: pam_unix(lightdm:session): session opened for user x(uid=1000) by (uid=0)
Feb 05 04:56:42 archlabs lightdm[767]: gkr-pam: unlocked login keyring
Feb 09 05:44:35 archlabs lightdm[486243]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=969) by (uid=0)
Feb 09 05:44:35 archlabs lightdm[486318]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 09 05:44:38 archlabs lightdm[486318]: gkr-pam: unable to locate daemon control file
Feb 09 05:44:38 archlabs lightdm[486318]: gkr-pam: stashed password to try later in open session
Feb 09 05:44:38 archlabs lightdm[486318]: pam_unix(lightdm:session): session opened for user x(uid=1000) by (uid=0)
Feb 09 05:44:38 archlabs lightdm[486318]: gkr-pam: unlocked login keyring
~►

I never tried to get rid of this error, it was never a problem: gkr-pam: unable to locate daemon control file

5

I’m honestly not sure what’s going on but it indeed looks like a leak from lightdm. I would switch to xinit or another DM and see if the problem persists. Doing a bit of googling shows this isn’t an uncommon issue with lightdm, some folks also suggest wrapping the X process if running it as root.

2 Likes