Can't refresh guide tv from XML file

Server Version#: .19.1.2621
Guide/Lineup name: XMLTV
Using XMLTV?: YES

Hello ,

i have difficulty to refresh my guide tv… i have this issue from a long time…

I need to restart my PMS and it’s working for 5 minutes and after that the issue reappearing again …
i click on refresh guide and it start and stop immediately without any reason…

i have tried a multiple provider and same problem …

Here’s the log files… :

Plex Media Server Logs_2020-04-04_19-06-44.zip (145.2 KB)

if you want the xml file , i can give you the file in a private file

Thanks!

Looks like it could not allocate sufficient memory for loading the guide data

Could you let me have the file that is not refreshing (zipped please)

Apr 04, 2020 19:05:12.577 [25108] ERROR - Error parsing XML: bad allocation.
Apr 04, 2020 19:05:12.577 [25108] DEBUG - EPG[xmltv]: failed to retrieve channel information during guide refresh
Apr 04, 2020 19:05:12.577 [25108] WARN - EPG[xmltv]: Failed to load EPG.

Here’s the file :

Thanks for your help

But i can give you an xml file from schedule direct … iptv-epg… etc… if i have too much information in the file… Plex can’t refresh the guide… and it’s a problem because i can’t edit the xml from schedule direct, zap2it… etc… :wink:

This 77.5 Mb xmltv file is giving memory allocation failures - so too big to handle.
I have referred it to our development team to look into it

Have you tried using smaller xmltv file ? And is that OK?

yeah it’s ok … if the file is smaller is ok … But if i use the original xml file from schedule direct… plex can’t handle it

Sorry sa2000…

My mistake… the issue is not solved at all …

Plex Media Server 1.19.3 has just been released to beta and has a fix for large xmltv files

See release note

  • (DVR) Server would sometimes fail to consume EPG data from certain XMLTV data files. (#11368)

Thanks,

So, the issue is still there… :wink:

And this version can’t play any files directly in PMS… :wink:

But the media play fine with client app …

Also since a few last updates i have this error too ..

Need to restart PMS to remove this error… and i fallback to this version 1.18.7.2457 i have no issue for recording and live tv…

Thanks!

This forum thread is about failures when refreshing the guide using a large xmltv file. 77 Mb file in the example provided earlier.

I have just tried using that file you provided before and we are no longer failing due to memory allocation errors.

If you believe the issue with large xmltv files is still happening, then please let me have the xmltv file that shows the problem and server logs covering the time when an EPG refresh is done and fails. Please make sure you use the current beta version of Plex Media Server for getting me the diagnostics/logs

Hello , here’s the new log file,

Plex Media Server Logs_2020-05-07_09-31-01.zip (8.2 MB)

The problem occur at 9:29

The new xmltv file…

https://drive.google.com/open?id=1fYp9-q4xg5VpvxoXZmwhDNJehJ0uYqUP

And what about the issue : the device does not tune the required channel?

I have this issue since a few update now… i can’t stay with the version 1.19.3.2764

I need to rollback to this version 1.18.7.2457

For this issue you can check at 09:29:20.403 on the logs maybe a problem with special character ?

Thanks for your help !

I will look at the xmltv issue. The tuning issue you mention is not relevant to this forum topic and should be raised as separate topic with the relevant diagnostics

You can cross refer here to the forum topic you raise for the tuning issue or if already raised - just link to it

Thanks for the logs and xmltv file. I have reproduced the memory allocation failures and crash when running out of memory. I have referred this back to the development team

The xmltv file is bigger than last one - 77Mb and now 120 Mb !

I know… but if i take a xml with schedule direct without change … you will have an xml above 120 mb… :wink:

If you want to check this issue too ..

Thanks!

How big is big for an XML file? The one use is about 200MB - generated from schedules direct using mc2xml.

While I didn’t go looking specifically, I never noticed any issues or failures using the generated file. My Plex server is a Synology NAS with 8GB ram.
I don’t know if the number of ‘enabled’ channels for a tuner matter - I only have 20 enabled (of 230+) for my HD Homerun Connect Quattro.

However, saying that, for the past 2-3 weeks, after upgrading to 1.19.1.2645 from version 1.18.something, I had been seeing double the normal memory usage (3.7GB Vs 1.8GB) for Plex server, but nothing major had changed in my setup that I could attribute that to.
With 1.19.3.2764 installed since yesterday I’m yet to see that same elevated memory usage, though I’d want give it a week or so to give all the scheduled tasks a chance to run through before confirming memory usage is back to ‘normal’.

Turned out to be very related - the memory allocation failures are occurring at the time of trying to tune the channel. Apologies for thinking it was not related

Until we have a fix for the 120Mb xmltv file that you are using, please try to get a smaller size. I think it is not just size but the depth of nesting level within the file that is also a factor.

Thanks for the reply,

i rescan channel on the tuner and see a change …

2 channels was remove from the detection… so for now i have no message like this : the device does not tune the required channel? will see in the next days…

i will wait for a fix for the xml …

thanks!

With a smaller size i have no problem… i change my provider for the XML from SD to iptv-epg and now i have no problem with 79mb xml …

I will create another topic for detection Series and movies on xml…

Thanks!

The fix for memory issues with large xmltv files has now been released in Plex Media Server beta 1.20.1.3213 released today

See Release Note: Plex Media Server

  • DVR) Would use excessive amount of memory when loading certain XMLTV guide files (#11501).