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 …
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…
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
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 !
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.
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…