[mythtv-commits] Ticket #8266: memory leaks in backend

MythTV mythtv at cvs.mythtv.org
Thu Apr 22 15:49:17 UTC 2010


#8266: memory leaks in backend
------------------------------+---------------------------------------------
 Reporter:  udovdh@…          |        Owner:  ijr       
     Type:  defect            |       Status:  closed    
 Priority:  major             |    Milestone:  unknown   
Component:  MythTV - General  |      Version:  0.22-fixes
 Severity:  medium            |   Resolution:  fixed     
  Mlocked:  0                 |  
------------------------------+---------------------------------------------
Changes (by danielk):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed in trunk:
 {{{
 On Thu, 2010-04-22 at 16:34 +0200, Udo van den Heuvel wrote:
 %CPU %MEM    VSZ   RSS TTY      STAT START   TIME C
 >  5.1  2.2 1706748 87208 ?       Ssl  Apr17  41:00 /usr/bin/myt
 >  5.2  2.2 1706748 86804 ?       Ssl  Apr17 116:20 /usr/bin/myt
 >  5.3  2.5 1706748 95612 ?       Ssl  Apr17 198:05 /usr/bin/myt
 >  5.4  2.6 1706748 102480 ?      Ssl  Apr17 278:57 /usr/bin/myt
 >  5.4  2.8 1706748 106516 ?      Ssl  Apr17 358:35 /usr/bin/myt
 }}}

 This sample shows zero growth in the memory requested by mythbackend.

 It seems you are confused by the meaning of the numbers here so I'll
 explain. VSZ is the total size of the libraries, executable, heap, and
 stack. This has not grown at all, which means MythTV has not requested any
 memory while recording 358 hours of programming per tuner. RSS is the the
 resident set, this is the actual RAM that the MythTV process has access
 to. This is allocated by the operating system based on what else you have
 running. RSS will never grow beyond VSZ.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/8266#comment:22>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list