1.2.0 text field "crashes"

Can you install the debug version of the client and then send over the
XiboDebug.log after it crashes. The file will be in the %ProgramFiles%
\Xibo folder and might well be large so please zip it if needed.

Cheers

Alex

This email carries a disclaimer, a copy of which may be read at http://learning.longhill.org.uk/disclaimer

Will do, hopefully it does it today.

Shahid

OK, so it finally failed again, but it only spit out a 2kb log file which doesn't look like it had much to offer other than when I configured the client. Is there any specific procedure to follow or is log generation supposed to be automatic with the debug version?

Are you sure you've got the right file. It should be logging a line each
time the file collection interval ticks etc - it should be XiboDebug.log
(not log.xml).

Alex

This email carries a disclaimer, a copy of which may be read at http://learning.longhill.org.uk/disclaimer

Finally recreated the error... I just sent an email with a log file. (It was still only 900kb or so...)

Thanks,
Shahid

Are you running over SSL? (not that this will have anything to do with the problem - its just interesting)

It looks like there are two items in your schedule for most of the log file - but only 1 is valid at a time.. the point where they swap over is the point where you are getting problems.

I believe that the resources for the second layout are not fully downloaded, or are detected to be changed just at the point the second layout is scheduled to come in - therefore the second layout will not play (does it go to splash screen?). What is a little odd is that then the connection to the web service becomes unresponsive.

I may need to add some extra logging and get you to try and recreate this again... I will have a look and let you know.

When you say crashed - did it revert to the splash screen?

Dan,

Yes, we're running over SSL (requirement of our IT security nut...he wouldn't give us a VLAN/server unless we did).

Regarding items in the schedule, the only thing that is running is that display's default layout (which is the text field with a custom background image). There are no other items in the scheduler. The last additional item scheduled was an image file (basically a poster) which ended back in early Sept. I didn't run the 1.2.0 upgrade until after that time.

It does not revert to the Xibo splash screen, the client (in most cases) continues to run with the single text region and background being displayed. However, the actual text within the region is missing, and the scrolling has stopped. It's just an image of a background with a bunch of white fields (where the text was) sitting on the screen.

As an interesting note, I can now recreate this on 2 machines whereas a few other clients (also with scrolling text only, but rare changes) have not really had any issues.

More info:

Completely uninstalled and reinstalled the application. Fully deleted all the files in the library location. Problem remains. Almost once every 24 hours or so it crashes.

Shahid,

I've been doing some work on this... and did find a few problems that might have caused this, mostly edge cases.

I should have a binary for you to try by the weekend, ill let you know.

Shahid, can you try these binaries and see if you still get the problem? They are non-debug binaries: http://dl.dropbox.com/u/353651/XiboClient.121-pre.zip

Got it and installed. Will keep you posted.

Binaries give following error,
"Your client is not of the correct version for communication with this server."

However, using those versions, it did crash in the same fashion.

Another note, I was going to take a screen cap to show exactly what was happening, but I got a Windows error message about being out of available memory (the machines have 1GB...), then upon Ctl+Alt+Del, the client just closed. I'm starting to think it more a hardware issue on my end as I've only been able to duplicate this behavior with a similar machine (which is an older set of hardware than my current "net top" machines.)

Will keep posted after more testing.

Sorry for the trouble. It looks like it was a hardware issue on my end. When the same layout is used on a different set of hardware, it seems to run fine with no problems. Thanks for your support!