id summary reporter owner description type status priority milestone component version severity resolution keywords cc mlocked 8944 MBE responsiveness slows until dead after adding SBE James Crow "I am running Mythbuntu amd64 9.10 on my MBE. Myth version is 0.23.1-26231. I recently added a SBE running Mythbuntu 10.04 amd64. The same exact version of Myth is running on both. With the SBE running the MBE slows its responsiveness down over time. Yesterday I restarted both the MBE and SBE at 5PM. By 11PM I was no longer able to view any recordings. Additionally it takes longer and longer to navigate the View Recordings screen and to get the status page in Mythweb. Recordings appeared to continue normally during this time. At 11PM I restarted both the MBE and SBE. I was immediately able to view the recording that failed a few minutes earlier. Both BE machines were running with -v network,extra,socket. This might be related to ticket 7608, but this is version 0.23.1 not 0.22. The uncompressed log files are between 60 and 70 MB per BE (5MB to 7MB compressed). For search aiding I see these types of errors in my log: 2010-09-15 20:00:04.059 MythSocket(1d574e0:-1): writeStringList: Error, socket went unconnected. 2010-09-15 20:00:06.805 MythSocket(1f91090:-1): writeStringList: Error, No data written on writeBlock (1 errors) 2010-09-15 20:00:06.888 MythSocket(1fe0b20:-1): writeStringList: Error, No data written on writeBlock (1 errors) 2010-09-15 20:00:18.784 MythSocket(1234010:-1): writeStringList: Error, No data written on writeBlock (1 errors) 2010-09-15 20:00:23.501 MythSocket(16b6720:-1): writeStringList: Error, socket went unconnected. 2010-09-15 20:00:38.349 MythSocket(7f1a486dc540:-1): writeStringList: Error, No data written on writeBlock (1 errors) 2010-09-15 20:30:44.349 MythSocket(7f1a48455050:-1): writeStringList: Error, socket went unconnected. 2010-09-15 20:30:44.982 MythSocket(7f1a48449300:-1): writeStringList: Error, socket went unconnected. I don't know if it is related or important, but I am also seeing some many mythcommflag segfaults in the system log. The message lists either libmythdb or some qt library." defect closed major unknown MythTV - General 0.23.1 medium Duplicate 0