https://bugs.kde.org/show_bug.cgi?id=368907
Mauro Carvalho Chehab <mchehab+...@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #44 from Mauro Carvalho Chehab <mchehab+...@kernel.org> ---
@Jan: thanks for identifying what part of Kaffeine was causing high CPU load!
Fixed on those two patches:
https://cgit.kde.org/kaffeine.git/commit/?id=7df55bf402a21778a945478ff44fca304fe06ab3:
dvbliveview: disable write ready notifications if nothing to write
The write notifier only makes sense if there's something to write.
Signed-off-by: Mauro Carvalho Chehab <mche...@s-opensource.com>
https://cgit.kde.org/kaffeine.git/commit/?id=a233d847ab7fdf13215f41e7240dcd307215ae42:
dvbliveview: better handle errors when writing to pipe
The current logic of writeToPipe() loops forever if an error
occurs. That causes CPU load to be 100%, as it will call write()
in non-block mode inside a loop until it succeeds. That's not
needed, as the write logic can already monitor the file descriptor
availability via QSocketNotifier.
--
You are receiving this mail because:
You are watching all bug changes.
