https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #22 from fanzhuyi...@gmail.com --- (In reply to Robin Bankhead from comment #21) > Created attachment 172739 [details] > perf.data.perfparser exported from hotspot, xz-compressed Thanks! It appears that a lot of time is spent doing context management in `QEventDispatcherGlib::processEvents`. A suspicious entry is `socketNotifierSourceDispatch`. It would appear that kglobalacceld is getting a lot of SocketNotifier events. One way to confirm that would be to use Gammaray on kglobalacceld, and check the events. The only place that kglobalacceld uses QSocketNotifier is using xcb record to listen to key and button presses and releases: https://invent.kde.org/plasma/kglobalacceld/-/blob/master/src/plugins/xcb/kglobalaccel_x11.cpp?blame=0#L89 If things are working as intended, there should be 1 event for each key/button press/release, which should be quite reasonable. On my end, this indeed is the behavior, as I can verify through Gammaray. Currently I have no idea why we might be getting a flood of events on your end. -- You are receiving this mail because: You are watching all bug changes.
