Its now quit a while i'm bussy with a very severe issue which we have on fast stb's such like vuduo2 or solo2, and ... in future this list will become bigger.
This issue is runtime errors caused by enigma2. One off the most problematic issues is playing dvd.iso files by dvd's which are pure like the original dvd , which means no shrink no reathoring. But strictly a dvd ripped with full dvd menus and the menu structure protection kept.
But You can see that on solo2 or vuduo2 there are more media and sometimes strange issues. Which cause the box to go into segfault or even worse complete deadlock loop. By this last only power off(by switch at the back or removing the power) can by used to solve. Unless You are familiar with telnet (or ssh) and now how to use killall command.
I'm now in discusion with mirakels and littlesat about the issues. But we can't agree on the cause.
p.s. this issue is living his own completely unpredictable life. And users are hit by it at the most expected times. yes it's really a p.i.s.
What I well now found out that somehow there is a relation to the use off eTimer into py modules. That is 100 % shure however mirakels and littlesat said it can't. practice proof that there is a relation to it.
which is the relation or mostlikely its a combination off use from etimer and somthing else.
Normally for a fast box such timers are not needed at all. If they are there it's a remainder off old days for very slow boxes. On the fast they just will cause bugs.
They are almost used as a hack (even a dirthy hack) for some other problems.
The nightmare off this all is that some issues Will only happen when you run the box in standard mode (init 3). From the moment You do a debug mode problems do not occur or can't be reproduced.
For users who update the vuduo2 and solo2 to the latest images and are dvd.iso file users they where hit before with segfault sometimes by starting a dvd enigma2 crash enigma2 restarted automatically. And when they retried it mostly worked out. Now they will not face a segfault anymore but a complete deadlock off stb with sandkeeper. After they set power off then on , restart the dvd they will be hit again with the deadlock. and ....
Well I do have one typ :
When You start a dvd.iso press ok and ok. (not a double click but ok (1second) ok) Then You wan't enter the deadlock. Minumum not a double ok but maximum 1 second in between.
It's clear that this is not a good thing.
Why this all happen :
1) It could be a stb's dvd driver issue always possible but to my opinion very unlikely.
2) The use off etimers in enigma2 Perhaps required on some old and slow boxes also used on more places as a work around and hack in enigma2.
I'm so what shure that by the fast boxes such as vuduo2 or solo2 the use off etimer is out off bound and the main cause to unstable behaviour.
But it will require real python enigma2 experts which are also c++ experts and very familiar with swig interface developpers. To find the cause.
