High CPU usage after suspend.

[yagi-tan]

Platform

Debian 12
Linux debian 6.1.0-17-amd64 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux

GPU, drivers, and screen setup

GPU: NVIDIA GeForce GT 730
Driver: nvidia-tesla-470-driver 470.223.02-2~deb12u1
Setup: Single monitor desktop.

glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 2048 MB
    Total available memory: 2048 MB
    Currently available dedicated video memory: 1750 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.223.02
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 470.223.02
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 470.223.02
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Environment

LXDE

picom version

vgit-702e3, v11. Problem appears starting from commit a28e221.

Diagnostics

**Version:** vgit-702e3

### Extensions:

* Shape: Yes
* RandR: Yes
* Present: Present

### Misc:

* Use Overlay: Yes
* Config file used: None

### Drivers (inaccurate):

NVIDIA

### Backend: glx

* Driver vendors:
 * GLX: NVIDIA Corporation
 * GL: NVIDIA Corporation
* GL renderer: NVIDIA GeForce GT 730/PCIe/SSE2

### Backend: egl

* Driver vendors:
 * EGL: NVIDIA
 * GL: NVIDIA Corporation
* GL renderer: NVIDIA GeForce GT 730/PCIe/SSE2

Configuration:

picom -b --backend glx --vsync

Steps of reproduction

1. Run picom, then suspend/standby the system.
2. Wakeup system.

Expected behavior

picom to have low CPU usage (0-2%) like before suspend.

Current Behavior

picom high CPU usage (~85%) after suspend. Restarting the process fixes the issue.

Log file

picom_702e30.tar.gz

[desbma]

I have the same exact issue, 100% CPU usage when returning from hibernation. A restart of the picom process fixes it. I also have this in my config file:

backend = "glx";
vsync = true;

I am on Arch Linux, with picom package version 11-4. This is a recent regression, as the issue was not occurring previously.

[yshui]

does it happen without vsync?

[absolutelynothelix]

can't reproduce on an intel gpu neither with the present vblank scheduler nor with the sgi_video_sync one.

[absolutelynothelix]

can reproduce on an nvidia gpu only with the sgi_video_sync vblank scheduler.

[yagi-tan]

does it happen without vsync?
can reproduce on an nvidia gpu only with the sgi_video_sync vblank scheduler.

Since there's something about vblank, should I disable this 'Sync to VBlank' config and try again without vsync?

[yshui]

@yagi-tan just set vsync = false in picom.conf

[yagi-tan]

Oh, picom --no-vsync --backend glx does fix the problem.

[absolutelynothelix]

@yagi-tan, you could also try PICOM_DEBUG=force_vblank_sched=present picom --backend=glx --vsync.

[yagi-tan]

@yagi-tan, you could also try PICOM_DEBUG=force_vblank_sched=present picom --backend=glx --vsync.

@absolutelynothelix Ahh, to force using present scheduler, isn't it? Yup, tested just now and that also works. Which one is better, present+vsync or sgi+no-vsync? Seems that both use similar CPU/RAM usage.

[yshui]

@yagi-tan please don't worry about the schedulers! and don't persist the PICOM_DEBUG environment variable, it's for debug only.

[yagi-tan]

@yshui I see. All right then, thanks all for quick responses. Feel free to close this issue.