Jump to content


Photo

Solo4K XMLTV import "crash the box"


  • Please log in to reply
110 replies to this topic

Re: Solo4K XMLTV import "crash the box" #101 doglover

  • Rytec EPG Team
  • 17,508 posts

+672
Excellent

Posted 11 September 2016 - 13:10

I have tested with old Germany3 test file and it still crashes.

 

And unfortunately both patches from IMS (he has 2 different versions), which replace the char array with a string, don't fix the problem. Box still crashes :(

 

Too bad...

 

Willy


Edited by doglover, 11 September 2016 - 13:10.

~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*


Re: Solo4K XMLTV import "crash the box" #102 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 11 September 2016 - 13:21

With valgrind I get this:
 

==1560== Invalid read of size 4
==1560==    at 0x4DEBF54: PySys_GetObject (in /usr/lib/libpython2.7.so.1.0)
==1560==  Address 0xc is not stack'd, malloc'd or (recently) free'd
==1560== 
<  1564.453> Backtrace1:
<  1564.497> Backtrace:
<  1564.508> ./enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x694A0]
<  1564.509> /lib/libc.so.6(__default_rt_sa_restorer) [0x51EF6C0]
<  1564.511> -------FATAL SIGNAL
==1560== Invalid read of size 4
==1560==    at 0x4DD4910: PyErr_Restore (in /usr/lib/libpython2.7.so.1.0)
==1560==  Address 0x4771c4af is not stack'd, malloc'd or (recently) free'd
==1560== 
==1560== 

It sounds more like a bug in python or swig. I'll test now OpenPli5. I think it uses other python and swig versions.


Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Solo4K XMLTV import "crash the box" #103 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 11 September 2016 - 13:37

With OpenPli5 I have no crash...


Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Solo4K XMLTV import "crash the box" #104 WanWizard

  • PLi® Core member
  • 71,236 posts

+1,842
Excellent

Posted 11 September 2016 - 13:54

Time for a new release then... ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Solo4K XMLTV import "crash the box" #105 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 11 September 2016 - 16:20

But even then it would be good to know the cause; it may have been 'accidentally' fixed.



Re: Solo4K XMLTV import "crash the box" #106 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 12 September 2016 - 13:52

4k for one desciption.... Sounds like overkill... When you read a lot of epg your ram fills up dramatically......

Any static array is always overkill. And at the same time it's always too small. Evil.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Solo4K XMLTV import "crash the box" #107 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 12 September 2016 - 13:54

With valgrind I get this:
 

==1560== Invalid read of size 4
==1560==    at 0x4DEBF54: PySys_GetObject (in /usr/lib/libpython2.7.so.1.0)
==1560==  Address 0xc is not stack'd, malloc'd or (recently) free'd
==1560== 
<  1564.453> Backtrace1:
<  1564.497> Backtrace:
<  1564.508> ./enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x694A0]
<  1564.509> /lib/libc.so.6(__default_rt_sa_restorer) [0x51EF6C0]
<  1564.511> -------FATAL SIGNAL
==1560== Invalid read of size 4
==1560==    at 0x4DD4910: PyErr_Restore (in /usr/lib/libpython2.7.so.1.0)
==1560==  Address 0x4771c4af is not stack'd, malloc'd or (recently) free'd
==1560== 
==1560== 
It sounds more like a bug in python or swig. I'll test now OpenPli5. I think it uses other python and swig versions.

Exactly what I already noticed. The bug is present on all platforms, but the MMU on ARM based SoC's is more strictly enforcing.

Edited by Erik Slagter, 12 September 2016 - 13:54.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Solo4K XMLTV import "crash the box" #108 Pr2

  • PLi® Contributor
  • 6,230 posts

+262
Excellent

Posted 12 September 2016 - 15:00

Hi,

 

What is preventing developers to apply the small patch I propose to make xmltvconverter more verbose to more easily track down issues with it?

 

http://forums.openpl...e-4#entry585847

 

This apply to this file:

 

https://github.com/O...ltvconverter.py

 

I read in another thread that you want to a patch so you can apply it easily and this is what I provide to you.

 

Pr2


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: Solo4K XMLTV import "crash the box" #109 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 12 September 2016 - 22:43

With valgrind I get this:
 

==1560== Invalid read of size 4
==1560==    at 0x4DEBF54: PySys_GetObject (in /usr/lib/libpython2.7.so.1.0)
==1560==  Address 0xc is not stack'd, malloc'd or (recently) free'd
==1560== 
<  1564.453> Backtrace1:
<  1564.497> Backtrace:
<  1564.508> ./enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x694A0]
<  1564.509> /lib/libc.so.6(__default_rt_sa_restorer) [0x51EF6C0]
<  1564.511> -------FATAL SIGNAL
==1560== Invalid read of size 4
==1560==    at 0x4DD4910: PyErr_Restore (in /usr/lib/libpython2.7.so.1.0)
==1560==  Address 0x4771c4af is not stack'd, malloc'd or (recently) free'd
==1560== 
==1560== 
It sounds more like a bug in python or swig. I'll test now OpenPli5. I think it uses other python and swig versions.

Exactly what I already noticed. The bug is present on all platforms, but the MMU on ARM based SoC's is more strictly enforcing.


Maybe we hit the same bug? :P

http://www.mono-proj...2/arm64-icache/
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Solo4K XMLTV import "crash the box" #110 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 14 September 2016 - 14:48

Hi,

 

What is preventing developers to apply the small patch I propose to make xmltvconverter more verbose to more easily track down issues with it?

 

http://forums.openpl...e-4#entry585847

 

This apply to this file:

 

https://github.com/O...ltvconverter.py

 

I read in another thread that you want to a patch so you can apply it easily and this is what I provide to you.

"backlog" is the cause :(


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Solo4K XMLTV import "crash the box" #111 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 14 September 2016 - 14:50

Maybe we hit the same bug? :P
http://www.mono-proj...2/arm64-icache/

Hmm, I don't think it's very plausible. I stick with my proposal.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.



18 user(s) are reading this topic

0 members, 18 guests, 0 anonymous users