If all media is invalid and only 1 layout exists Xibo will crash

Bug #654175 reported by Dan Garner
38
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Xibo
Fix Released
Critical
Dan Garner
1.2
Fix Released
Critical
Dan Garner
1.3
Fix Released
Critical
Dan Garner

Bug Description

The most likely scenario for this to happen would be for the cachemanager.xml file to be corrupted.

Tags: dotnetclient

Related branches

Revision history for this message
Dan Garner (dangarner) wrote :

I think the only solution is for the:
- cachemanager to be aware of layouts and their content
- schedulemanager to be aware of the cachemanager

In this way the active schedule could contain only layouts that have at least 1 valid piece of media.

tags: added: dotnetclient
Revision history for this message
Rui Bernardino (rui-bernardino) wrote :

I did some testing on what I think is the same issue, here's what happens with my dotnet client: if you create a layout where the first region is empty (as in the first one of the xlf file) and this is the only layout, the player will always crash, regardless of the other regions content. If I delete the first region, the next one will become the first and the same problem will occur.
If there are 2 layouts in the schedule, the player doesn't crash but the content of the 'buggy' layout gets merged (literally) under the second layout. A 3rd layout and presumably others don't get affected and display normally.

Revision history for this message
Alex Harrington (alexharrington) wrote :

Thanks Rui

Can you try the same tests with the 1.2.1 pre-release?

http://dl.dropbox.com/u/353651/XiboClient.121-pre.zip

Cheers

Alex

Revision history for this message
Rui Bernardino (rui-bernardino) wrote :

Just tried the pre-release but exactly the same problem occurs. I always clear the 'Media Library' directory and the xlf files are OK.

Thanks!

Revision history for this message
Alex Harrington (alexharrington) wrote :

Rui

You need to clear the cacheManager.xml file too otherwise it will crash for sure (as it assumes that once a file has been downloaded it will remain there).

Alex

Revision history for this message
Alex Harrington (alexharrington) wrote :

In fact if you could take a copy of your cacheManager.xml file before moving/renaming it that would be great as it may be useful to Dan - I'm not sure.

Alex

Revision history for this message
Rui Bernardino (rui-bernardino) wrote :

No change. With a single layout (when it crashes), 'cachemanager.xml' simply contains:

--- BEGIN
<?xml version="1.0" encoding="utf-8"?>
<CacheManager xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <_files />
</CacheManager>
--- END

Thanks

Revision history for this message
Alex Harrington (alexharrington) wrote :

Additional patch for this:

On the server side, in "lib/service/xmdssoap.class.php" on line 203 - change

    $SQL .= " ORDER BY RecordType";

to

    $SQL .= " ORDER BY RecordType DESC";

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.