Opened 8 years ago

Closed 8 years ago

#10132 closed Bug Report - General (Unverified)

Memory Leak in trunk

Reported by: joe@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords: Memory Leak
Cc: Ticket locked: no

Description

Running Mythbuntu nightly builds, experiencing a significant memory leak while watching video on 10/24/11 and 10/26/11 nightly build. It appears that whenever the OSD is displayed, approximately 20MB of RAM is consumed and not released; causing the system to start using swap after about 30 minutes of normal viewing on my system with 768MB of RAM.

Once the system starts using swap, it appears to use it in a sub-optimal fashion and I begin to experience pauses that appear as alsa buffering errors in the log, these pauses are most significant whenever the OSD is displayed.

Change History (6)

comment:1 Changed 8 years ago by robertm

Status: newinfoneeded_new

Please provide valgrind logs.

"Uses a lot of memory" != "Memory leak" until proven with Valgrind.

comment:2 Changed 8 years ago by Raymond Wagner

Milestone: 0.24.2unknown
Severity: highmedium

reset defaults...

comment:3 Changed 8 years ago by joe@…

I have been trying to figure out valgrind, but I'm not sure exactly how to use it. Perhaps this is not a "leak" but it is certainly a symptom of something.

All I know is that I can start watching a show and have 256MB of RAM free and 0 swap used. After an hour I have used nearly all of the free ram and about 256MB of swap and am experiencing stalls in playback especially just before the OSD is displayed; and it kills me to use the menus because it will stall for minutes as the drive thrashes trying to load the menu.

This is a frontend only machine running VDPAU and the Terra Theme. I see no noticeable memory issues navigating the menus, browsing shows, the program guide, or my 500+ video collection... it's just while watching a recording, I would think that, since the video is streamed from the back-end, memory usage would be minimal.

comment:4 Changed 8 years ago by robertm

Joe, since nobody else is reporting this, and it can't easily be reproduced, we really need you to come through with valgrind logs for us to be able to do anything with this, unless it begins to affect a developer who will run it themselves. If you need some assistance with valgrind there is likely someone on the users list who can assist you.

comment:5 Changed 8 years ago by joe@…

This can be closed. It appears to have cleared up after upgrading from Ubuntu 10.10 to 11.10 and upgrading to the latest nightly build.

Still more swap activity than I am used to, but the system doesn't appear to use it nearly as aggressively as before and the swap hits are not nearly as disruptive.

comment:6 Changed 8 years ago by danielk

Resolution: Unverified
Status: infoneeded_newclosed
Note: See TracTickets for help on using tickets.