Project

General

Profile

Bug #3274

Extremely high memory usage which eventually leads to crash

Added by Steve Smith about 9 years ago. Updated about 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Crashes
Target version:
-
Start date:
2015-11-05
Due date:
% Done:

0%

Estimated time:
Found in version:
4.1-855-g646a663 and previous versions
Affected Versions:

Description

Occasionally, for no apparent reason something happens which causes the memory usage to get out of control and if the computer runs out of ram a crash of the operating system will occur. I have enclosed a debug log.
Thanks


Files

tvheadend.debug.log (478 KB) tvheadend.debug.log Steve Smith, 2015-11-05 18:06

History

#1

Updated by Jaroslav Kysela about 9 years ago

Do you have tvhomerun tuner ?

#2

Updated by Steve Smith about 9 years ago

No. Its a Hauppauge HVR-2250. I did have the hdhomerun packages installed on my system though. I have uninstalled them.

#3

Updated by Paolo Zeppegno about 9 years ago

Do you have timeshift enabled?

#4

Updated by Steve Smith about 9 years ago

Timeshift has never been enabled.

#5

Updated by Jaroslav Kysela about 9 years ago

Really no idea. These things are most difficult to debug. I plan to add some memory allocation statistics.

#6

Updated by Steve Smith about 9 years ago

Well, like I said it does it out of the blue. I have been using various versions of tvheadend for about a year and a half and it has happened maybe ten times. I am a programmer myself (PHP) and understand how difficult some bugs are to debug. I do believe the bug has been there for a long time.

#7

Updated by Jaroslav Kysela about 9 years ago

Perhaps, you may try to run tvheadend through valgrind:

cd git/tvheadend
valgrind --leak-check=full --show-reachable=yes ./build.linux/tvheadend

Do the scan on all muxes and then press Ctrl-C in the console with valgrind if it shows something.

#8

Updated by Steve Smith about 9 years ago

I am now running the program through valgrind as per your instructions to try and find this memory leak. I haven't done this before so I don't know what kind of resource usage we are talking here or if my computer can handle it. I guess only time will tell. Even if my computer can handle it, it may be a while before it gives me any memory issues. I remember it happening after a program had finished auto-recording possibly right before the next one started, however the next program which was supposed to record never showed up in the log.

Also available in: Atom PDF