Xibo

Client crash/exit after connection problems

Asked by Bartek

Hello,

I have small problem with some clients placed in locations witch 3g connections.
Some times when 3g connection become unstable and I can't reach remote location's ip camera and vnc server, Xibo crashes on those remote terminals. When connection is stable again I can log in to terminal and view camera steam, there is windows desktop only on display, no errors on the screen etc. There is no problem with starting client again and everything starts working ok for next 5-10 days.
Maybe there is no catch for some strange connect-error exception or something?
It is definitly no power-off problem, router, terminal & camera uptimes indicates that there was no power break during location disconnection.

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Alex Harrington
Solved:
Last query:
Last reply:
Revision history for this message
Dan Garner (dangarner) said : 		#1

Just to make sure we are on the same page...

You suspect that there might be a problem when Xibo is used on an unstable connection? I found a piece of code the other day which would sometimes have generated an exception if a connection died "mid call".

This code is in the 1.0.5 milestone, but after being reviewed needs a little more work. I have linked the bug to this question.

Revision history for this message
Bartek (czajka) said : 		#2

Yes, i suspect that unstable connection can crash 1.0.3/1.0.4 client

I'm not sure that I undestand correctly, You found that suspect code in 0.3/0.4 and it will be fixed in 0.5 or suspect code is in 0.5 version in effect of fixing bug reported by Mariusz?

Revision history for this message
Best Alex Harrington (alexharrington) said : 		#3

Hi Bartek

Dan means that the code is in all currently released versions of the Xibo client. We hope to fix this in 1.0.5.

As this has been converted to a bug, you should mark the question as solved as its progress will be tracked by the bug report.

Many thanks

Alex

Revision history for this message
Bartek (czajka) said : 		#4

Thanks Alex Harrington, that solved my question.