[VU+ Zero4K] Possible Bug: OpenVix crashes when using zap-buttons

[Manno]

Since the latest update OpenVix crashes when using the zap-buttons.
This happened 3 times in the last 2 days.
Log reports added, maybe this will clear things up.:thumbsup:

 

[birdman]

This could be the same as the crash reported here:

They both occur straight after two messages about pixmap failures, and are both SIGABRTs.

 

[Manno]

A week ago downloaded the latest update.
Just the box crashed again, now with 33 pixmap failures .......

 

[Manno]

Something goes very wrong........

 

[birdman]

From: Enigma2_crash_2022-08-09_00-14-08.log
< 92364.0502 > [InfoBarGenerics] setEvent text: 22 62C 627 647 627 ....

This is actually a debug message for bad encoding in an EPG description.
Also, lots of:

< 92364.0543> [eTextPara] unicode U+fb8e not present
< 92364.0547> [eTextPara] unicode U+fbfe not present
< 92364.0551> [eTextPara] unicode U+fb90 not present

Perhaps providing some more details about which Vix version you are using, which plug-ins you have installed etc might help?

 

[Huevos]

more details about which Vix version

This is contained in the crash log.

Please try "Simple_Ten_Eighty" skin and see if the result is the same.

 

[birdman]

This is contained in the crash log.

But plugins are not...

However, this look ominous:

< 92341.1586> [eWindowStyleManager] getStyle(style_id=1): NOT FOUND

Looking at the code which produces this message (eWindowStyleManager::getStyle in lib/gui/ewindowstyle.cpp) it prints that message, but makes no attempt to do anything else, so the ePtr<eWindowStyle> &style parameter is never set, which might explain the crash.

 

[Huevos]

But plugins are not...

However, this look ominous:



Looking at the code which produces this message (eWindowStyleManager::getStyle in lib/gui/ewindowstyle.cpp) it prints that message, but makes no attempt to do anything else, so the ePtr<eWindowStyle> &style parameter is never set, which might explain the crash.

Have you got a fix for that?

 

[Manno]

This is actually a debug message for bad encoding in an EPG description.
Also, lots of:

Perhaps providing some more details about which Vix version you are using, which plug-ins you have installed etc might help?

Version 6.2.008.

The file lib/gui/ewindowstyle.cpp is not found in the stb.

 

[twol]

Version 6.2.008.

The file lib/gui/ewindowstyle.cpp is not found in the stb.

Thats because its part of the enigma nucleus

 

[birdman]

Have you got a fix for that?

No.
I don't even know what a Style Managers is (nor why you might not have one, nor why you are allowed to have more than one).

 

[birdman]

Have you got a fix for that?

No.
I don't even know what a Style Manager is (nor why you might not have one, nor why you are allowed to have more than one).

However, it's possible that the branch that produces the message (and doesn't set style) could add:

                style = new eWindowStyleSimple();

This is based on what eWindow::eWindow does when it gets no style. (And there are 2 other pieces of code that call getStyle(style) then don't use the result).
But I have no idea as to how to test this. Should I just submit a PR anyway?

 

[Huevos]

If there is an obvious error, yes.

 

[birdman]

If there is an obvious error, yes.

PR is:

https://github.com/OpenViX/enigma2/pull/788

It compiles, which is all I can test...

 

[twol]

PR is:

https://github.com/OpenViX/enigma2/pull/788

It compiles, which is all I can test...

This was looked at and one of the originators added an assert, which was instantly removed as unhelpful ….. hence the also unhelpful debug line was added which is not normally seen!
I am guessing this is a better solution than either from the originators.

 

[Manno]

I did a little experiment and found out that the crash is caused by an tv station entry in the zap list.
The tv station causing the crash is AVA Family on the TurkmenÄlem/MonacoSat 52E 10845 V.
As soon this tv station becomes part of the ZAP list and i pull up the zap list with the buttons the box crashes,
i think it has something to do with the used characters/style (Persian) in the program/station information just like Birdman explains i a previous post about the EPG..................
Maybe someone can confirm this ?? :thumbsup:

 

[birdman]

….. hence the also unhelpful debug line was added which is not normally seen!

That's the real bug - why it doesn't find the style in the first place.
But (hopefully) keeping enigma2 running is always better.