Changes between Initial Version and Version 3 of Ticket #6969


Ignore:
Timestamp:
Sep 4, 2009, 2:08:30 AM (15 years ago)
Author:
danielk
Comment:

For some reason we are transmitting a RECORDING_LIST_CHANGE DELETE event to a mythweb socket that has already been disconnected. We do check for disconnected sockets in the transmit code, but that isn't working. The easy workaround is to just add "if (sock->socket() < 0) continue;" on line 917 of mainserver.cpp before the upref, but I'd honestly the PlaybackSock? should be handled by HandleDone?(), because it appears this is a slow memory leak of PlaybackSock? classes which will grow with each PlaybackSock? connection...

However, I'm not sure that this socket issue would have caused the backend to become unresponsive. It appears the backend is running after this and nothing is preventing it from accepting new connections. This may have something to do with the mythweb side of things, with which I'm not familiar. I'll fix the backend side of the issue, and if the problem persists I'll pass this ticket on to xris or kormoc.

This may also be related to #6955.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6969

    • Property Owner changed from Isaac Richards to danielk
    • Property Status changed from new to assigned
    • Property Version changed from unknown to head
    • Property Milestone changed from unknown to 0.22

  • Ticket #6969 – Description

    initial v3  
    11I upgraded to trunk 21644 and now when I delete a recording from mythweb's recorded programs page, the ajax interface says "1 request pending" for a long time (approx 1 minute or so) before finally refreshing.  From this point on the backend in non-responsive.  I have a backtrace of the backend and the logfile (all, nodatabase, noupnp).
     2g