[mythtv-commits] Ticket #11352: Leak in MythPainter::DrawTextLayout

MythTV noreply at mythtv.org
Mon Jan 14 10:18:30 UTC 2013


#11352: Leak in MythPainter::DrawTextLayout
-------------------------------------+-------------------------------------
 Reporter:  Bradley Baetz            |           Type:  Bug Report -
  <bbaetz@…>                         |  General
   Status:  new                      |       Priority:  minor
Milestone:  unknown                  |      Component:  MythTV - General
  Version:  0.26-fixes               |       Severity:  medium
 Keywords:                           |  Ticket locked:  0
-------------------------------------+-------------------------------------
 I've been noticing increased memory usage with mythfrontend in 0.26 vs
 0.25. Its been happening since I upgraded shortly after 0.26 was released.
 The symptom is a gradual leak (as shown with top/free), but sometimes the
 memory usage increases by 50-100M over an hour or so.

 I haven't been able to work out what the trigger for this difference is,
 but I've been running my frontend under valgrind for the past couple of
 weeks to track it down.

 The attached log (Using 0.26-fixes-72bca07 plus the patch for #11329, on
 ubuntu 12.04) is from a run that had an uptime of just under a day. there
 was one 30 min recording (HDHR) during that time, plus watching a couple
 of recorded shows and videos. It was cleanly shutdown (exit from the
 mainmenu) (by this stage watching a recording was stuttering because the
 box was swapping. This whole setup is a bit fragile perf-wise - valgrind
 on an HP microserver only works with vdpau...)

 the log shows 112M of "possibly lost" allocations. A bit over 80M of that
 comes from MythPainter::DrawTextLayout, so I'm assuming that that's where
 the leak is. However there's also a bit more from other things (eg
 MythPainter::DrawRoundRect), so maybe its something else leaking?

 Using the Steppes theme, in case that matters

 I've also attached a log (valgrind.donothing) of mythfrontend where all I
 did is wait a few minutes and then shut it down again (as a baseline)

 valgrind was run as "valgrind --leak-check=full --show-reachable=yes
 --undef-value-errors=no --num-callers=50 --log-file=/tmp/valgrind.%p" with
 the patch from
 https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1096323 applied.

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/11352>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center


More information about the mythtv-commits mailing list