Opened 10 years ago

Closed 10 years ago

#6955 closed defect (fixed)

EIT scanner leaks file descriptors

Reported by: Joel <mythtv@…> Owned by: danielk
Priority: minor Milestone: 0.22
Component: MythTV - EIT Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

If I have the EIT scanned enabled, even for only a few channels, it leaks file descriptors. Every 5 minutes, two sockets get opened and never get closed until I restart mythbackend. At that rate, it hits the 1024 limit in 42 hours. I suspect that the two sockets opened correspond to the two receivers on the HDHomeRun. I'm not sure where in the code this is happening, but here is an strace of a thread which opens a file descriptor and never closes it.

http://ebel.mybox.org/fdleak.trace

fd 24 is the one in question. This thread also appears to communicate with the hdhomerun on fd 7.

Change History (6)

comment:1 Changed 10 years ago by Stuart Auchterlonie

Owner: changed from Stuart Auchterlonie to danielk
Status: newassigned

comment:2 Changed 10 years ago by danielk

Milestone: unknown0.22
Version: 0.21-fixeshead

Joel can you please provide a "mythbackend -v socket,network,extra" log.

This may be related to #6969.

Please test with trunk as the needed debugging is not present in 0.21-fixes.

comment:3 Changed 10 years ago by Joel <mythtv@…>

Sadly I'm not in a good position to be testing with trunk at the moment. I'll try to set up trunk in a VM and use my hdhomerun, but it won't completely duplicate my primary setup which also includes two pchdtv-5500's.

comment:4 Changed 10 years ago by danielk

(In [21725]) Fixes #6969. Refs #6955. Fixes a file descriptor + memory leak.

This may be a fix for #6955. If not, please provide -v socket,network,extra logs for the backend for a long enough time to catch this leak (15 mins?)

comment:5 Changed 10 years ago by danielk

Status: assignedinfoneeded

comment:6 Changed 10 years ago by danielk

Resolution: fixed
Status: infoneededclosed

No info provided. This was probably fixed in [21725].

Note: See TracTickets for help on using tickets.