We still do not know what the issue is.Now we know what the problem is - how do we fix it??
- Why does a scan return (sometimes?) Channelnames with odd characters?
- Is it really the odd character in the channelname which causes the crash?
- Or is it some odd character inside the EPG datastream itselfe? (which was the cause of crashes in the past)
Usually the only way to find out if it is the data in the received EPG is to enable one channel after the other for EPG grabbing.
And continue to do that until you find the corrupted one. Then we need an complete TS dump of that channel to analyze and find the data the EPG grabber does not like (if it even is the garbber causing the issue).
That kind of issue is annoyingly hard to track down.