--- Comment #18 from Mauro Carvalho Chehab <mchehab+...@kernel.org> ---
(In reply to José JORGE from comment #17)
> (In reply to Mauro Carvalho Chehab from comment #16)
> > 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.
> Any hint on how to profile? Thanks.
> > Maybe this could be a reflex of EPG parsing, as reported on this bug:
> > https://bugs.kde.org/show_bug.cgi?id=371579
> I don't think so, as the 100% CPU sometimes stops only by clicking on stop,
> then play again.
Bug #371579 was fixed upstream. Could you please test if this solved the issue
You are receiving this mail because:
You are watching all bug changes.