https://bugs.kde.org/show_bug.cgi?id=480885
--- Comment #38 from Dashon <dashonww...@pm.me> --- (In reply to Zamundaaa from comment #37) > Okay, that worked. > About 5% of the CPU usage is in drmModeAddFB2WithModifiers, which is not > great, but more importantly 77% is in a drmIoctl in the framebuffer > destructor, which will be either > https://invent.kde.org/plasma/kwin/-/blob/ > bbfffec6d6efcb6ab81fc57a08430892b0b50e52/src/backends/drm/drm_buffer.cpp#L69 > or > https://invent.kde.org/plasma/kwin/-/blob/ > bbfffec6d6efcb6ab81fc57a08430892b0b50e52/src/backends/drm/drm_buffer.cpp#L70 > They get called when apps update the cursor image or their window, which > causes KWin to update the cursor or screen with a different buffer, which > explains why you see different behavior with different apps. > > I don't know what the kernel driver is doing in the drm ioctl - hotspot just > shows ??? - but it's supposed to be pretty much free, so this is almost > certainly a driver bug. Please report it at > https://forums.developer.nvidia.com/c/gpu-graphics/linux/148 Thanks for your time. I'll make sure to report it. I somehow knew it would end up back in Nvidia's hands. -- You are receiving this mail because: You are watching all bug changes.
