Hi,
I figured out why it was happening, there was a bad recording, so
whenever either a frontend selected the file in watch recordings, or
when mythweb tried the recorded_programs page it would do this.
Deleting the dodgy recording was the only way to stop it doing this
every time.
I've never se
Isaac Richards wrote:
> On Wednesday 06 July 2005 05:20 pm, Mark wrote:
>
>>Not sure if this in any use at all, but I was running in GDB when I got
>>the old 'Waiting for a thread' problem, so gzipped a backtrace here:
>>http://irishmark.co.uk/myth-backtraces/waiting_for_thread.tar.gz
>>
>>This is
On Wednesday 06 July 2005 05:20 pm, Mark wrote:
> Not sure if this in any use at all, but I was running in GDB when I got
> the old 'Waiting for a thread' problem, so gzipped a backtrace here:
> http://irishmark.co.uk/myth-backtraces/waiting_for_thread.tar.gz
>
> This is from a master with 2 slaves
Not sure if this in any use at all, but I was running in GDB when I got
the old 'Waiting for a thread' problem, so gzipped a backtrace here:
http://irishmark.co.uk/myth-backtraces/waiting_for_thread.tar.gz
This is from a master with 2 slaves, the master having recently been
restarted.
Mark
__