Bug #1125
Memory Leak during streaming http
0%
Description
i use only http with IPTV
I try some tests with htop
recording live and playing this records => no problem about memory leak
streaming live tv with Wifi the memory increase about 10Mo/mn and in wired ethernet about 500ko/mn
From Adam Sutton
On the basis of what you've said above I think this definitely sounds like a genuine bug and I'm thinking it could be related to discarded packets not being cleaned up.
https://www.lonelycoder.com/redmine/boards/5/topics/3501
History
Updated by pierre cha about 12 years ago
for more information ,if i do a "pause"(timeshifting) on the stream , the memory continue to increase .perhaps it will better to do a temporary file to avoid saturating the memory when the network is of poor quality .
Updated by Adam Sutton about 12 years ago
There is no timeshift/pause support in tvheadend. This will be client buffering.
Updated by John Törnblom about 12 years ago
Could you try latest git version and see if the problem is still there? There have been some changes to the streaming and hopefully your problem was fixed on its own.
Updated by pierre cha about 12 years ago
hello
i do some stream about 30 minutes and it seems that memory is about 1,2% (192Mb of total memory) at the beginning to grow up to 8% in the first minutes and stabilizes after between 6 and 8% .it looks good .
it seems to me that the stream is more fluid with much less break of the stream.
When I cut the stream, the memory does not go down .Is this normal ?
I will do some longer tests with several stream .
thanks
PS .i see a problem with mediacontainer "passtrough" when I want abort recording => i get "transaction aborted" and tvheadend seems very slow .
Updated by John Törnblom about 12 years ago
- Assignee set to John Törnblom
I will try to figure out a way to increase performance. There is a pull request for this but it needs to be integrated with master in a proper way. It's not a quick fix so I need some time to think it through.
Updated by Adam Sutton about 12 years ago
I think this is a duplicate of #1054, which I'm going to have a look at as I've now read the report and understand the problem.
Adam
Updated by Adam Sutton about 12 years ago
- Status changed from New to Need feedback
Updated by Adam Sutton about 12 years ago
- Status changed from Need feedback to Fixed
I'm going to, for now, assume the problem is fixed and close this issue. If the recent update does not resolve the problem we'll re-open.