There was a complete signal outage yesterday + a power outage recently. I
don't know which messages should be atributed to which cause.
Getstream is definitely not immune to complete signal outage, not even with my
hackpatch.
I *guess* that it would be fine with the watchdog disabled.. (just
** Changed in: getstream (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175944
Title:
getstream quits with SIGABRT when ANY of the tuners loses signal
To
UPDATE: Progress!
The stall was traced to a the while loop in dvr_input_ts ( dvr.c:68 )
When psi_reassemble does not increase off, it gets called again with the same
arguments - inf-loop
I believe that that can happen only when section-len == 0.
I have no idea where is that coming from nor
** Attachment added: GDB Stacktraces at the aborts
https://bugs.launchpad.net/ubuntu/+source/getstream/+bug/1175944/+attachment/3681137/+files/stacktraces.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: Not a real fix, but at least it removes the crash symptom.
https://bugs.launchpad.net/ubuntu/+source/getstream/+bug/1175944/+attachment/3681138/+files/NOT_A_FIX-only-a-hack.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The attachment Not a real fix, but at least it removes the crash
symptom. seems to be a patch. If it isn't, please remove the patch
flag from the attachment, remove the patch tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
correction:
If the multiplex from the *affected (signal loss)* tuner was streamed
somewhere.
Well, the watchdog is really necessary.
The event loop gets stuck eventually when one of the tuners has poor signal
(and perhaps when I attempt to watch it?).
So far it seems that increasing the
I disabled the watchdog.
Temporary signal outage on one tuner does not affect other tuners for at least
30s.
If the multiplex from the tuner was streamed somewhere, a warning
appears on the console, saying demux: read in dvr_read returned with
errno 75
I wonder whether the libevent loop gets
According to the source code the SIGABRT watchdog thread should only be active
when compiled with DEBUG
That also produces a notice on every http stream start and end (also matches my
observations)
I'll try building it without debug to see whether it's really locking
up, or only the watchdog
Just as I expected. Adding new tuner to capture a weaker dvb-t multiplex
causes a sigabrt every now and then, usually at least once per hour,
causing disruptions to all multiplexes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
10 matches
Mail list logo
