https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #48 from coe...@gmail.com ---
(In reply to coekbe from comment #45)
> Note how
> there are never any writes or reads on the FIFO at all in the test app. Yet
> the hammering goes on.
>
I was confused about this. This is actually the correct
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #47 from Mauro Carvalho Chehab ---
(In reply to José JORGE from comment #46)
> Yes a big thanks for all, it was beyond my abilities...
Yeah, fixing performance issues usually is not trivial.
> For an end user, is
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #46 from José JORGE ---
Yes a big thanks for all, it was beyond my abilities...
For an end user, is there an idea when an official release will bring this fix?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #45 from coe...@gmail.com ---
(In reply to Mauro Carvalho Chehab from comment #43)
>
> That's the expected behavior. Basically, reads and writes are buffered
> internally at the Kernel. When such buffer is filled, a write to the
> buffer
https://bugs.kde.org/show_bug.cgi?id=368907
Mauro Carvalho Chehab changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #43 from Mauro Carvalho Chehab ---
(In reply to coekbe from comment #41)
> Created attachment 106508 [details]
> Demo app to show infinite signal emission
>
> It looks like using a write notifier on a FIFO (or an
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #42 from coe...@gmail.com ---
Created attachment 106509
--> https://bugs.kde.org/attachment.cgi?id=106509=edit
A patch using a read notifier
Another patch fixing the 100% cpu usage
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=368907
coe...@gmail.com changed:
What|Removed |Added
CC||coe...@gmail.com
--- Comment #41 from
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #40 from Jan Palus ---
Looks like this was it! After applying last patch issue did not occur within
10min of constant channel switching. Thanks a lot Mauro!
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=368907
Mauro Carvalho Chehab changed:
What|Removed |Added
Attachment #106506|0 |1
is
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #38 from Mauro Carvalho Chehab ---
Created attachment 106506
--> https://bugs.kde.org/attachment.cgi?id=106506=edit
Disable notifier if no data
(In reply to Jan Palus from comment #36)
> Looks like it's still the
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #37 from Jan Palus ---
And just to be clear -- not empty counter continues to increase with the same
pace once bug is triggered and everything works fine (TV runs smoothly), it's
just high CPU usage in the background
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #36 from Jan Palus ---
Looks like it's still the same, but I'm not really sure whether we are on the
same page -- writeToPipe() is not looping. It is rather called a lot once the
bug is triggered. I've made following
https://bugs.kde.org/show_bug.cgi?id=368907
Mauro Carvalho Chehab changed:
What|Removed |Added
Attachment #106501|0 |1
is
https://bugs.kde.org/show_bug.cgi?id=368907
Mauro Carvalho Chehab changed:
What|Removed |Added
Attachment #106498|0 |1
is
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #33 from Mauro Carvalho Chehab ---
(In reply to Mauro Carvalho Chehab from comment #32)
> Ok, error 11 is EAGAIN. I suspect that the pipeline buffer is full.
> Probably, VLC is too slow to handle the DVB channel
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #32 from Mauro Carvalho Chehab ---
Created attachment 106500
--> https://bugs.kde.org/attachment.cgi?id=106500=edit
Wait 100ms before retrying after an error
(In reply to Jan Palus from comment #31)
> Thanks for
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #31 from Jan Palus ---
Thanks for the patch. Unfortunately it does not change much -- issue is still
there. New warning is constantly printed when kaffeine operates normally:
08-07-17 14:23:17.447 [Warning ]
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #30 from Mauro Carvalho Chehab ---
Created attachment 106498
--> https://bugs.kde.org/attachment.cgi?id=106498=edit
Don't ignore errors when writing to libVLC pipe
(In reply to Jan Palus from comment #29)
> It
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #29 from Jan Palus ---
It appears once the issue is triggered DvbLiveViewInternal::writeToPipe() is
called thousands of times a second but buffers is always empty.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #28 from Jan Palus ---
Some random observations:
1. For some reason issue is much easier to reproduce if kaffeine is run from
gdb. Usually takes single channel change to trigger the problem
2. With enabled
https://bugs.kde.org/show_bug.cgi?id=368907
Szymon Stefanek changed:
What|Removed |Added
CC||pra...@kvirc.net
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #26 from Jan Palus ---
Created attachment 106452
--> https://bugs.kde.org/attachment.cgi?id=106452=edit
callgrind output
Also attaching callgrind output
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #25 from Jan Palus ---
I experience the same issue (version 2.0.10). Seems like it starts to happen as
soon as some glitch in decoding is encountered -- video artifacts, green screen
which kaffeine recovers from within
https://bugs.kde.org/show_bug.cgi?id=368907
Jan Palus changed:
What|Removed |Added
CC||jan.pa...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=368907
stetsbeq...@womentie.de changed:
What|Removed |Added
CC||stetsbeq...@womentie.de
--- Comment
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #22 from Mauro Carvalho Chehab ---
(In reply to José JORGE from comment #21)
> (In reply to Mauro Carvalho Chehab from comment #18)
> > Bug #371579 was fixed upstream. Could you please test if this solved the
> >
https://bugs.kde.org/show_bug.cgi?id=368907
Michal Donat changed:
What|Removed |Added
CC||mic...@donat.cz
--
You are
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #21 from José JORGE ---
(In reply to Mauro Carvalho Chehab from comment #18)
> Bug #371579 was fixed upstream. Could you please test if this solved the
> issue for you?
Issue not solved as of today's GIT. I could get
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #20 from Mauro Carvalho Chehab ---
(In reply to José JORGE from comment #19)
> (In reply to Mauro Carvalho Chehab from comment #18)
> > Bug #371579 was fixed upstream. Could you please test if this solved the
> >
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #19 from José JORGE ---
(In reply to Mauro Carvalho Chehab from comment #18)
> Bug #371579 was fixed upstream. Could you please test if this solved the
> issue for you?
Thanks, but I suppose I have to checkout form
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #18 from Mauro Carvalho Chehab ---
(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
> >
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #17 from José JORGE ---
(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
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #16 from Mauro Carvalho Chehab ---
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
https://bugs.kde.org/show_bug.cgi?id=368907
yuli...@mailbox.org changed:
What|Removed |Added
CC||yuli...@mailbox.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=368907
johan.claudebreunin...@gmail.com changed:
What|Removed |Added
CC||johan.claudebreuninger@gmai
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #14 from knossos456 ---
oups in wrong section
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #13 from knossos456 ---
my diseqc propblem is solved, I've changed the switch.
I have now problems on some DVB-S2 - 8PSK transponder.
DVB-S2 QPSK seem to be OK in all cases.
For example, i can't scan :
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #12 from José JORGE ---
(In reply to Mauro Carvalho Chehab from comment #11)
> option is accepted there. You could try those:
> --no-video-title-show -V xcb_glx
> or:
> --no-video-title-show -V xcb_xv
>
>
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #11 from Mauro Carvalho Chehab ---
(In reply to Mauro Carvalho Chehab from comment #10)
> (In reply to José JORGE from comment #8)
> > (In reply to knossos456 from comment #7)
> > I use vlc 2.2.4. It is important to
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #10 from Mauro Carvalho Chehab ---
(In reply to José JORGE from comment #8)
> (In reply to knossos456 from comment #7)
> > If you dont use virtual adapters, please notice also that kaffeine 2.0x use
> > vlc as dvb
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #9 from knossos456 ---
Ok, understanded.
Have VLC same probleme with a recoded HD stream ?
Have you installed Ubuntu from scratch or upgraded a previous version ?
What will done the command vdpauinfo ?
On my side,
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #8 from José JORGE ---
(In reply to knossos456 from comment #7)
> If you dont use virtual adapters, please notice also that kaffeine 2.0x use
> vlc as dvb core, and perhaps your version of Vlc is not correct, version >
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #7 from knossos456 ---
I'm on Ubuntu 16.04 LTS.
I roll back to Kaffeine 1.22 too because Kaffeine 2.0x have crach problemes
with virtual dvb adapter (dvbloopback) wich is need to descramble.
If you dont use virtual
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #6 from Oscar Fuentes ---
Kubuntu 16.10 comes with Kaffeine 2.0.4.
As far as I recall I never experienced the same problem with Kaffeine 1.x, for
the 8 years I'm using it.
(Currently I'm using Kaffeine 1.2.2 again due to
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #5 from knossos456 ---
And wich version of Kaffeine for each (exact 2.0x version)?
Have you same problem with Kaffeine 1.22 based on Xnine ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #4 from Oscar Fuentes ---
Mine is an ATI HD6450 (also R600) using the radeon non-propietary driver.
No problems with VLC.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368907
--- Comment #3 from José JORGE ---
(In reply to knossos456 from comment #2)
> Have you same problem with VLC (because newest Kaffeine is based on VLC
> core) ?
> For me and ATI 5450, all is OK (VLC and Kaffeine) for VDPAU and
https://bugs.kde.org/show_bug.cgi?id=368907
knossos456 changed:
What|Removed |Added
CC||knossos...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=368907
Oscar Fuentes changed:
What|Removed |Added
CC||o...@wanadoo.es
--- Comment
50 matches
Mail list logo