Problems with Hangups Browsing Videos

[rickgillyon]

Okay, this is driving me a bit nuts. Browsing through imported videos in Android MiniClient using Gemstone, the cursor suddenly stops on one video folder (different one every time) and Sage becomes completely unresponsive (this client only). No keys work (the long-press menu will appear but not do anything Sage-related, just exit). After a minute or so the screen goes blank and the MiniClient exits.

Any idea what's going wrong? If I go back in straight away to the MiniClient it will do it again, but if I clear out GeneratedThumbnails first it's okay.

I'm attaching a server log, just a short 3-minute one, where it happened. MiniClient involved is 4f424f464853 (although it happens on others too).

Any ideas where the issue is? Thanks!

[KarylFStein]

Maybe this?

https://forums.sagetv.com/forums/sho...510#post612510

[rickgillyon]

Ah, that looks like it, thanks. It's weird though, the folders I see it hang up on, I don't see any really long filenames. Can it be caching a different folder than the one you're on?

[KarylFStein]

As I recall it seemed really random on which folder it froze. Maybe it is doing some pre-caching or something.

[rickgillyon]

Originally Posted by KarylFStein

As I recall it seemed really random on which folder it froze. Maybe it is doing some pre-caching or something.

That would make sense. Do we know what the limit is? How many characters?

[stuckless]

Originally Posted by rickgillyon

That would make sense. Do we know what the limit is? How many characters?

The problem is that Android has a max filename limit of 256 chars. Ultimately the fix for this requires that the client advertise what it's filesystem limits are to the server, and then the server can ensure that any filename it sends is less than this.

I tried to "fix" this on the miniclient, but, it's too complicated, since I need to keep the original name that sagetv sends me, to send it back to the server, so there is a lot of mapping going on.

When sagetv sends filenames to the miniclient for images, it includes the full path of that file, so, if you have a filename like,

c:/programfiles/sagetv/images/some_really_long_name_with_complete_epside_information.jpg

then that entire path (including the directory) is converted to a filename and sent as the unique filename for the image... so this where you can quite easily start to go over the 256 character limit.

[rickgillyon]

Thanks. Can I tell Sage/Client/Gemstone/Phoenix or everywhere to not bother with thumbnails? The images I already get are fine for me.

[Tiki]

Originally Posted by stuckless

The problem is that Android has a max filename limit of 256 chars. Ultimately the fix for this requires that the client advertise what it's filesystem limits are to the server, and then the server can ensure that any filename it sends is less than this.

I tried to "fix" this on the miniclient, but, it's too complicated, since I need to keep the original name that sagetv sends me, to send it back to the server, so there is a lot of mapping going on.

When sagetv sends filenames to the miniclient for images, it includes the full path of that file, so, if you have a filename like,

c:/programfiles/sagetv/images/some_really_long_name_with_complete_epside_information.jpg

then that entire path (including the directory) is converted to a filename and sent as the unique filename for the image... so this where you can quite easily start to go over the 256 character limit.

Is it not possible to just add some error checking on the mini-client that checks the length of the file name and just skips it or displays a placeholder image (like a broken link on a web page) if it is too long?