Crashing when zapping through IPTV channels

[lincsat]

I've gone back to 5.1.002 for now but will try new releases when available

I may modify the suls output to match my generated EPG and use that as the bouquets look pretty good

[twol]

I've gone back to 5.1.002 for now but will try new releases when available

I may modify the suls output to match my generated EPG and use that as the bouquets look pretty good

Thats one of the Suls benefits, standardised bouquets, that can be easily tailored/sequenced to suit your needs and matched up to your EPG

[lincsat]

Just an update, tried today with build 5.1.006 and get the same issue

<   597.775> [eEPGCache] next update in 2 sec
<   597.776> [eDVBServicePMTHandler] ok ... now we start!!
<   597.776> [eDVBDemux] open demux /dev/dvb/adapter0/demux8
<   597.776> [eDVBSectionReader] DMX_SET_FILTER pid=0
enigma2: ../Python-2.7.13/Objects/frameobject.c:671: PyFrame_New: Assertion `f->f_code == code' failed.
<   597.846> PC: 761c7b88
<   597.846>     00000000 fffffffe 00000000 00000020
<   597.846>     00000003 7ffe6e48 00000000 00000000
<   597.846>     00000000 00000000 000771de 00000001
<   597.846>     00100073 ccd23db8 00000000 61586540
<   597.846>     00000000 7ffe6e48 00000006 7ffe6f80
<   597.846>     76907d80 61586540 00000000 006b1b78
<   597.846>     761e3404 761c86a4 00000010 00000000
<   597.846>     762f7e00 7ffe6db0 6158b578 761c7b14
<   597.846> Backtrace:
<   597.847> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x461F8C]
<   597.847> /lib/libc.so.6(gsignal) [0x761C7B8A]
<   597.847> -------FATAL SIGNAL (6)

I'm treating myself to an Ultimo 4K, so will see how that goes.

[lincsat]

I've now got the Ultimo, thanks to eBay's 20% off voucher

I can confirm that this problem does not manifest in the Ultimo4K, even with the same settings imported from the Duo2.

[abu baniaz]

Are you still able to conduct some tests? If so, you have a PM

There were only two Dev builds between 5.1.002 and 5.1.003.

[lincsat]

Not right now M8 as I'm onto the Ultimo4k. I can say that using the same 5.1.007 build on the Ultimo4k as on the Duo2, the problem does not manifest, so it looks like it's Duo2 (or maybe Vu+ V2 boxes) specific. I have tried the same IPTV list on an unsupported receiver running ViX and it's also good on that.

[sunday96]

Did you get the issue resolved? I am having exactly same issue on my duo2 with image 5.1.018. Box just crashes at will on IPTV channel zapping...

[bbbuk]

Did you get the issue resolved? I am having exactly same issue on my duo2 with image 5.1.018. Box just crashes at will on IPTV channel zapping...

Debug logs would be helpful

The log, as posted in post #18, is fatal signal. I've seen this error, albeit rarely (at least for me), on other boxes including my Solo2.

This, for me, happened even before I started using IPTV so I don't believe it's IPTV issue. I don't think this error is limited to duo2 neither.

Is this same error you're getting?

[lincsat]

Still get occasional crashes, less so since changing to an Ultimo4K. I don't have any logs but from memory it's a fatal signal related to libc.so.6

[lincsat]

Had a crash tonight that looks like it's ExtEPlayer3 related. I've trimmed the log and obfuscated the IPTV addresses

[abu baniaz]

For search/references purposes

<260105.323> [eDVBServicePlay] cutfile not found!
<260105.323> [eDVBServicePlay] no cue sheet
<260105.324> Traceback (most recent call last):
<260105.324>   File "/usr/lib/enigma2/python/Navigation.py", line 89, in dispatchEvent
<260105.324>   File "/usr/lib/enigma2/python/Components/PerServiceDisplay.py", line 17, in event
<260105.324>   File "/usr/lib/enigma2/python/Components/Sources/CurrentService.py", line 26, in serviceEvent
<260105.324>   File "/usr/lib/enigma2/python/Components/Element.py", line 86, in changed
<260105.325>   File "/usr/lib/enigma2/python/Tools/RedirectOutput.py", line 7, in write
<260105.325> UnboundLocalError: local variable 'args' referenced before assignment
<260105.325> [ePyObject] (CallObject(<bound method Navigation.dispatchEvent of <Navigation.Navigation instance at 0x9114f9b8>>,(10,)) failed)

[sunday96]

Debug logs would be helpful

The log, as posted in post #18, is fatal signal. I've seen this error, albeit rarely (at least for me), on other boxes including my Solo2.

This, for me, happened even before I started using IPTV so I don't believe it's IPTV issue. I don't think this error is limited to duo2 neither.

Is this same error you're getting?

Thanks for your response.

I have never had channel zapping crash until last week and I have been using IPTV for about 4 years now.

I had the fatal signal in the log too, posting below for any eagle-eyed person that can help debug the log. (Please note that any IPTV connection details in the log are just dummy data)

Cheers

[bbbuk]

Thanks for your response.

I have never had channel zapping crash until last week and I have been using IPTV for about 4 years now.

I had the fatal signal in the log too, posting below for any eagle-eyed person that can help debug the log. (Please note that any IPTV connection details in the log are just dummy data)

Cheers

Just looks like fatal signal that I and others have had. I personally don't worry about it because it's rare for me. I don't think anyone has ever come up with reason for it or how to solve the issue (that I know of).

How often does it happen for you?

Has anything changed since last week when it started happening like install/remove plugin or image update?

[birdman]

Had a crash tonight that looks like it's ExtEPlayer3 related. I've trimmed the log and obfuscated the IPTV addresses

Totally different issue - you should open a new thread.
And ExtEPlayer3 (presumably) seems to be logging to syslog, rather than just printing to stderr. So it's filling up the system log (it's also far too verbose).

[sunday96]

Just looks like fatal signal that I and others have had. I personally don't worry about it because it's rare for me. I don't think anyone has ever come up with reason for it or how to solve the issue (that I know of).

How often does it happen for you?

Has anything changed since last week when it started happening like install/remove plugin or image update?

Nothing has changed really and it happens all the time, I can reproduce it.

And I wouldn't have worried about it too but just that it crashes the box and cause a restart. I have a SoloSE with the same setup as the duo2 and never had a reboot on that. I will go for clean flash and see if the issue get resolved.

Edit: The SoloSE I haven't updated in a while and still on 5.0.020 (About June 2017 image)

Cheers