Slow response in Live TV Guide - ImageProcessor Error

[jonas8890 2]

I've been experiencing an issue for the past few weeks where the live TV guide is very slow to respond. The rest of the GUI is snappy. The Android app seems to be affected more strongly than the web client. If I scroll to a future time I see that the time does not scroll with the guide data and I also see that if I click on a program it will take roughly 60 sec to respond. Also takes 60 seconds to respond to other button presses (home, app back, android back).

 

Server log shows a lot of ImageProcessor errors:

2017-11-22 16:13:09.655 Error ImageProcessor: Error encoding image
	*** Error Report ***
	Version: 3.2.36.0
	Command line: C:\Users\Pete\AppData\Roaming\Emby-Server\system\EmbyServer.dll
	Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Processor count: 4
	Program data path: C:\Users\Pete\AppData\Roaming\Emby-Server\programdata
	Application directory: C:\Users\Pete\AppData\Roaming\Emby-Server\system
	System.ArgumentNullException: Value cannot be null.
	Parameter name: image
	   at SkiaSharp.SKBitmap.FromImage(SKImage image)
	   at Emby.Drawing.Skia.SkiaEncoder.CropWhiteSpace(SKBitmap bitmap)
	   at Emby.Drawing.Skia.SkiaEncoder.GetBitmap(String path, Boolean cropWhitespace, Boolean forceAnalyzeBitmap, SKCodecOrigin& origin)
	   at Emby.Drawing.Skia.SkiaEncoder.GetBitmap(String path, Boolean cropWhitespace, Boolean autoOrient)
	   at Emby.Drawing.Skia.SkiaEncoder.EncodeImage(String inputPath, DateTime dateModified, String outputPath, Boolean autoOrient, Nullable`1 orientation, Int32 quality, ImageProcessingOptions options, ImageFormat selectedOutputFormat)
	   at Emby.Drawing.ImageProcessor.<ProcessImage>d__29.MoveNext()
	System.ArgumentNullException
	   at SkiaSharp.SKBitmap.FromImage(SKImage image)
	   at Emby.Drawing.Skia.SkiaEncoder.CropWhiteSpace(SKBitmap bitmap)
	   at Emby.Drawing.Skia.SkiaEncoder.GetBitmap(String path, Boolean cropWhitespace, Boolean forceAnalyzeBitmap, SKCodecOrigin& origin)
	   at Emby.Drawing.Skia.SkiaEncoder.GetBitmap(String path, Boolean cropWhitespace, Boolean autoOrient)
	   at Emby.Drawing.Skia.SkiaEncoder.EncodeImage(String inputPath, DateTime dateModified, String outputPath, Boolean autoOrient, Nullable`1 orientation, Int32 quality, ImageProcessingOptions options, ImageFormat selectedOutputFormat)
	   at Emby.Drawing.ImageProcessor.<ProcessImage>d__29.MoveNext()

I'm running the latest Windows server 3.2.36.0. Can't recall what version I first experienced this issue. I also recently did a reinstall of the server.

 

Logs are attached. Please let me know if there's any other debugging or info I can provide. Thanks for any help.

server-63646963928.txt

[Luke 42085]

Hi there, can you try installing 3.2.40 from the website and see how that compares? thanks !

[jonas8890 2]

I tried the latest server version but I'm still seeing the same behavior in the android guide and the same errors in the log.

 

I haven't seen any similar reports from other users in the forums, but I don't think there's anything particularly unique about my setup. I'm using serverWMC for live TV, but that's about it.

server-63647034861.txt

[Luke 42085]

I wouldn't worry about the image errors in the log. What device are you running this with? Is the app up to date?

[jonas8890 2]

I'm running this on last year's Pixel. The app is the latest available in the play store. A family member reported similar issues with the iOS app on her iphone. The android log is attached if there's anything useful in there.

35ad5cb2-827a-490c-aec2-b70a9faba9da.log

[Luke 42085]

how many channels do you have?

[jonas8890 2]

571 channels (cable card through Time Warner).

 

I went into WMC and filtered out all of the channels I don't get, on-demand channels, duplicates, and stuff I'll never watch. Now it's down to 152. It's definitely more responsive now.

 

Did you guys change something in the guide? This wasn't happening a month ago when I had 571 channels.

[Luke 42085]

Not that I can think of. In fact, the response times in your server log look OK to me. We will be revamping the data loading in the guide in the near future though. Thanks.