https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #16 from Mauro Carvalho Chehab <mchehab+...@kernel.org> --- a "100% CPU" usage, doesn't really mean that the CPU is 100%. The way the Kernel generates this stat is by identifying how many times the Kernel task scheduler is idle, e. g. if there's no pending task to be scheduled, it increments a counter. If such counter is not incremented, it shows 100% usage. So, a 100% CPU only means that, every time the scheduler is called, there's a task waiting to be awake. The way Kaffeine works is that there are multiple synchronous tasks running: - tasks that receive DVB audio, video and EPG streams; - tasks to parse MPEG data, decompress it and display the video via libVlc. If any of this task happens as often as the scheduler is called, it will show 100% CPU usage. It is hard to discover what task is taking more time without profiling it. One could run a profiler to check what task is consuming more time, in order to identify the culprit. Maybe this could be a reflex of EPG parsing, as reported on this bug: https://bugs.kde.org/show_bug.cgi?id=371579 -- You are receiving this mail because: You are watching all bug changes.
