[Mut@nt HD2400] Constant Crashing Using Webif

[JeanReno]

I'm getting constant GUI crashes since updating to 4.2.012 earlier today. I'm currently using Webif to view the box. Crash log attached.

View attachment Enigma2_crash_2016-11-08_12-39-00.log

 

[Andy_Hazza]

You haven't installed WebIf via plugin's have you?


Sent from my iPhone using Tapatalk

 

[JeanReno]

No, it's a pretty clean install with very few plugins.

 

[JeanReno]

It's a problem with the screenshot gathering by the looks of things, Webif works fine until I try to view a screenshot.

It seems to cause a crash if I set the refresh to 0-2 seconds. Manually refreshing seems to be ok, but I can't be sure.

 

[SpaceRat]

aio-grab has never been made for movie creation
0-2 seconds is a far too low interval.

OWIF could probably catch that error and enforce an interval of at least 3 sec (Which probably would still be too low for some low end boxes), but that won't change anything about its inability to show live video through the screenshot feature.

 

[JeanReno]

Strange that it's never been an issue using '0 seconds' before. It's not 'live video' even at 0 seconds and I don't expect it to be, but it's useful for remote menu operation and changing of settings.

 

[SpaceRat]

Why would you want the screenshot to update 20 times in 20 seconds if you do a key press only like every 5 seconds?

 

[birdman]

OWIF could probably catch that error and enforce an interval of at least 3 sec...

That test should be done at the server end - just in case you have multiple Web interface clients running to it.
It needs a cross-thread variable (and/or mutex-locked code?) of when the last one was done and should refuse to progress until a suitable time has elapsed.

 

[EMJB]

Why would you want the screenshot to update 20 times in 20 seconds if you do a key press only like every 5 seconds?

As far as I am concerned, because sometimes the result of a key press is a "please wait while.." type of message (notably pressing List), so selecting automatic updates every second covers all eventualities. This works OK for me on my Xtrend 10K and Vix 4.1.

EMJB

 

[birdman]

Possibly fixed by this (going solely by the description text):

[URL]https://github.com/oe-alliance/e2openplugin-OpenWebif/commit/9dd3241ab041fb25a5fa31af6963fb4b025d8657[/URL]

 

[SpaceRat]

Yes, should be.

 

[SpaceRat]

Auto-Refresh every 0.1 seconds (Yes, 1/10th of a second): Works
But clicking on Refresh very fast and often can still make it crash.

 

[birdman]

Auto-Refresh every 0.1 seconds (Yes, 1/10th of a second): Works
But clicking on Refresh very fast and often can still make it crash.

Unless you've installed the file personally then you won't have it running - it's not in any release yet (it will be in the next one).

 

[SpaceRat]

I'm one of the devs, of course I have it already

 

[Bangord30]

I sent my log to WOS few nights ago as my duo 2 has been crashing for a good few weeks now(every update done as and when) and I've been reflashing but upon reading the log it's always something to do with openwebif. Closed it down on my pc and not used it for a few nights and box been fine.

Sent from my VF695 using Tapatalk

 

[Bangord30]

Possibly fixed by this (going solely by the description text):

[URL]https://github.com/oe-alliance/e2openplugin-OpenWebif/commit/9dd3241ab041fb25a5fa31af6963fb4b025d8657[/URL]

Guys, how in plain English when there has been a pull request(?) or a file amended on github, do you amend this file on your own box? I can never see a simple download file button on github?! Maybe I'm missing but always looks confusing to me

 

[ccs]

You can "view" the .py file and then there is a "raw" button, which you can use to see the whole file without numbering, and you can right click raw and "save target as", or select all and copy and paste.

I'm sure this isn't the way, but it does work.

 

[birdman]

I'm one of the devs, of course I have it already

So post the crash log.

 

[Ev0]

So post the crash log.

Here is mine (different box and image, but i'm sure the crash will be the same)

 

[birdman]

Here is mine (different box and image, but i'm sure the crash will be the same)

That log just contains garbage characters once it comes to the log part:

xb9\x10\r\x01U<\x01\xc1\xf5\xadc\xdci&l\xfc\x17\xbbd\xd1/\xf4\xb9\x0e\x05\x9d\xfbm\xcf\xbeMup\xabo\x00\x7f\xcbG$\xfbW\x0b\xf0.....

so nothing useful.
It could be a memory overwrite within enigma2, or a damaged file-system on your debug log storage device.