Hi, I maintain the eepg plugin, if you send me a stack trace, or add it as an issue here: http://projects.vdr-developer.org/projects/plg-eepg I will look into it. I'm using the eepg plugin for a very long time without any problem. For the memory leak, I have not I have not reproduced it in my usage of vdr, so if someone can provide me with the steps to reproduce it, which channel it happens on and so on I will try to fix it.
Regards
On Sun, 14 Apr 2013 10:05:54 +0200 Dimitar Petrovski dimeptr@gmail.com wrote:
Hi, I maintain the eepg plugin, if you send me a stack trace, or add it as an issue here: http://projects.vdr-developer.org/projects/plg-eepg I will look into it. I'm using the eepg plugin for a very long time without any problem. For the memory leak, I have not I have not reproduced it in my usage of vdr, so if someone can provide me with the steps to reproduce it, which channel it happens on and so on I will try to fix it.
I haven't associated the leak with any channel. I don't use VDR for live viewing very much, mainly for recording and playback. The memory seems to leak even when I'm not actively using VDR at all. I thought it must be caused by "harvesting" the EIT in the background. I think I tried using valgrind once, but it completely failed to notice the leak for some reason (perhaps valgrind doesn't apply to plugins?).
VDR also used to "spam" my syslog with messages including the names of programmes, but it doesn't seem to be doing that any more. I think it was caused by something slightly amiss with Freeview's EPG that VDR thought it should warn about. This could be related to the leak, but I haven't used EEPG for a while.
The other reason for me to use the patch is for Freeview HD's EIT. The encoding is exactly the same as Freesat's but I think the difference is that it still uses standard PIDs instead of non-standard ones. So EEPG would have to detect the encoding by using the flag bytes at the start of the string instead of by the PID they're from.
The other reason for me to use the patch is for Freeview HD's EIT. The encoding is exactly the same as Freesat's but I think the difference is that it still uses standard PIDs instead of non-standard ones. So EEPG would have to detect the encoding by using the flag bytes at the start of the string instead of by the PID they're from.
I would like to second what Tony states here. When I used the EEPG plugin (quite a long time ago), it failed to decode Freeview HD EPG because it did not support the encoded EPG delivered on the standard PID. So this is why I use the patch instead of the EEPG plugin.
I spent some time trying to figure out how to modify the plugin to suit my needs but it was beyond my understanding and I gave up.
Here's another thought for anyone using eepg current git (which you _should_ try before declaring there are bugs and so on)... Are you patching VDR with a bunch of other crap, possibly something that is the true cause of your problems? If eepg git works perfect for some users, but not for others then there's likely some difference(s) between these setups involved. A problem with eepg can easily be a symptom of some other issue.
Eepg is working fine here, even running in background by vdr's EPG scan. The single issue I have is that the plugin is filling the log with various messages, even if I set loglevel to a low value (1).
Regards,
István
On 2013.04.14. 11:05, Dimitar Petrovski wrote:
Hi, I maintain the eepg plugin, if you send me a stack trace, or add it as an issue here: http://projects.vdr-developer.org/projects/plg-eepg I will look into it. I'm using the eepg plugin for a very long time without any problem. For the memory leak, I have not I have not reproduced it in my usage of vdr, so if someone can provide me with the steps to reproduce it, which channel it happens on and so on I will try to fix it.
Regards
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
I have been toggling between eepg and LoadEPG plugins.. I haven't tried the patch above, perhaps it would be better?
eepg seems to crash occasionally, and also I had this weird problem that all channels have Polish category-fields.. :)
LoadEPG doesn't crash, doesn't speak Polish, but is not automatic so you have to launch it from crontab or something. Also it had the timezone problem for which I provided a patch earlier in this list, but that only affects people who watch satellites not from their own timezone.
-- Teemu
2013/4/14 Füley István aironet@tigercomp.ro:
Eepg is working fine here, even running in background by vdr's EPG scan. The single issue I have is that the plugin is filling the log with various messages, even if I set loglevel to a low value (1).
Regards,
István
On 2013.04.14. 11:05, Dimitar Petrovski wrote:
Hi, I maintain the eepg plugin, if you send me a stack trace, or add it as an issue here: http://projects.vdr-developer.org/projects/plg-eepg I will look into it. I'm using the eepg plugin for a very long time without any problem. For the memory leak, I have not I have not reproduced it in my usage of vdr, so if someone can provide me with the steps to reproduce it, which channel it happens on and so on I will try to fix it.
Regards
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Log level can be set to 0. I will review the loginig info and silence it as much as possible. And set the default logging to 0 in git. Eepg is working fine here, even running in background by vdr's EPG scan. The single issue I have is that the plugin is filling the log with various messages, even if I set loglevel to a low value (1).
Regards,
István
On 2013.04.14. 11:05, Dimitar Petrovski wrote:
Hi, I maintain the eepg plugin, if you send me a stack trace, or add it as an issue here: http://projects.vdr-developer.**org/projects/plg-eepghttp://projects.vdr-developer.org/projects/plg-eepg I will look into it. I'm using the eepg plugin for a very long time without any problem. For the memory leak, I have not I have not reproduced it in my usage of vdr, so if someone can provide me with the steps to reproduce it, which channel it happens on and so on I will try to fix it.
Regards
______________________________**_________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-**bin/mailman/listinfo/vdrhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
______________________________**_________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-**bin/mailman/listinfo/vdrhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Am 14.04.2013 17:32, schrieb Dimitar Petrovski:
Log level can be set to 0. I will review the loginig info and silence it as much as possible. And set the default logging to 0 in git. Eepg is working fine here, even running in background by vdr's EPG scan. The single issue I have is that the plugin is filling the log with various messages, even if I set loglevel to a low value (1).
BTW:
You have recieved the patch for eepg to move the tables from external to internal and have even reworked the patch. How about spreading it, it minimizes the risk of a memory leak.
- Mario
Do you refer to: http://projects.vdr-developer.org/issues/903 I was waiting for the author to test it. I have local git branch where it is implemented
On Mon, Apr 15, 2013 at 7:49 AM, Mario Schulz drcms@arcor.de wrote:
Am 14.04.2013 17:32, schrieb Dimitar Petrovski:
Log level can be set to 0. I will review the loginig info and silence it as much as possible. And set the default logging to 0 in git. Eepg is working fine here, even running in background by vdr's EPG scan. The single issue I have is that the plugin is filling the log with various messages, even if I set loglevel to a low value (1).
BTW:
You have recieved the patch for eepg to move the tables from external to internal and have even reworked the patch. How about spreading it, it minimizes the risk of a memory leak.
- Mario
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr