- Moderator
- #141
Georgius, it's not easy to reproduce with DVB EPG but i think i'm able to force by tuning channel, so i will post log from this test :
I have 4 DVB-IP card. (1 / 6 / 7 and 8 ID)
TF1 TNT is mapped to DVB-IP ID card 8.
6TER TNT is mapped to DVB-IP ID card 1 and 8.
From SetupTV, i'm timeshift TF1 TNT.
From MP, i try to tune 6TER TNT (so it try Card1)
So it can't tune because TF1 and 6TER are not on same mux.
So it try to use DVB-IP card 1 while TF1 is already running.
In that special case, memory goes up each time i try to tune 6TER (it take 5mb on each tune and so on and so on).
So i suppose when i have see TvService to 1.7GB of ram, it's because in 24H it try to grab some EPG between few channel (wrongly mapped).
But that lead to the fact that something is wrong, it's maybe not a memory leak lol.
And here the timeshift file timeout is not respected, so maybe we need an event to force to close IPTV tuning when it reach timeshift timeout.
Not sure if it helps, i will log the above scenario with 3 tuning try (6TER channel).
Seb.
I have 4 DVB-IP card. (1 / 6 / 7 and 8 ID)
TF1 TNT is mapped to DVB-IP ID card 8.
6TER TNT is mapped to DVB-IP ID card 1 and 8.
From SetupTV, i'm timeshift TF1 TNT.
From MP, i try to tune 6TER TNT (so it try Card1)
So it can't tune because TF1 and 6TER are not on same mux.
So it try to use DVB-IP card 1 while TF1 is already running.
In that special case, memory goes up each time i try to tune 6TER (it take 5mb on each tune and so on and so on).
So i suppose when i have see TvService to 1.7GB of ram, it's because in 24H it try to grab some EPG between few channel (wrongly mapped).
But that lead to the fact that something is wrong, it's maybe not a memory leak lol.
And here the timeshift file timeout is not respected, so maybe we need an event to force to close IPTV tuning when it reach timeshift timeout.
Not sure if it helps, i will log the above scenario with 3 tuning try (6TER channel).
Seb.
France