Yep, it looks like the backend is deadlocked. Can you update to
7372, repeat this in gdb and then hit "Ctrl-C" and get me the
results of "thread apply all bt". I'd like to know where each
thread is.
Here's one from 7386.
mythbackend.log.bz2
Description: Binary data
backend_deadlock.txt.bz2
Bruce Markey wrote:
This sounds too weird to be true and I wanted to get someone to
verify this before filing a bug. Before starting to compose a
message, I found this thread =).
I too was having trouble with the second invocation of live TV
but was having trouble debugging it. A little divide
This sounds too weird to be true and I wanted to get someone to
verify this before filing a bug. Before starting to compose a
message, I found this thread =).
I too was having trouble with the second invocation of live TV
but was having trouble debugging it. A little divide and conquer
led to thi
Jon Whitear wrote:
Mark Weaver wrote:
You could try running it normally, making it break and then doing
attach in gdb. You should be able to get a backtrace that way.
Thanks for the tip. I started front- and backend normally, made it
break, then ran gdb as follows:
server awstats # ps f
Mark Weaver wrote:
You could try running it normally, making it break and then doing
attach in gdb. You should be able to get a backtrace that way.
Thanks for the tip. I started front- and backend normally, made it
break, then ran gdb as follows:
server awstats # ps fax
16020 ?S
Yep, it looks like the backend is deadlocked. Can you update to
7372, repeat this in gdb and then hit "Ctrl-C" and get me the
results of "thread apply all bt". I'd like to know where each
thread is.
I'm afraid I can't make it break under gdb. I spent ages existing and
re-entering Live TV and it
Daniel Kristjansson wrote:
Yep, it looks like the backend is deadlocked. Can you update to
7372, repeat this in gdb and then hit "Ctrl-C" and get me the
results of "thread apply all bt". I'd like to know where each
thread is.
I'm afraid I can't make it break under gdb. I spent ages existing and
On Sun, 2005-10-02 at 09:20 +1000, Jon Whitear wrote:
> Here's what the backend's doing at the time:
> 2005-10-02 08:40:26.401 MainServer::HandleAnnounce Playback
> 2005-10-02 08:40:26.402 adding: epia as a client (events: 0)
> 2005-10-02 08:40:26.409 adding: epia as a remote ringbuffer
>
> Note
These logs were not made with up to date SVN, so they don't tell me
exactly what is wrong. Maybe your lib path is broken?
Anyway it seems to have been caused by a RingBuffer shutdown issue.
Try revision 7368 or later, it may be fixed there.
==
Please make sure you are running with up to date
On Fri, 2005-09-30 at 09:07 +1000, Jon Whitear wrote:
> > Can you regenerate this doing the minimal number of things that
> > will trigger the problem?
> >
> > And, please mark the backend log with each action you've taken in
> > the UI, at the appropriate time.
> >
> > These logs are filled with a
> Can you regenerate this doing the minimal number of things that
> will trigger the problem?
>
> And, please mark the backend log with each action you've taken in
> the UI, at the appropriate time.
>
> These logs are filled with all kinds of unrelated things like
> generating previews, making time
On Thu, 2005-09-29 at 23:13 +1000, Jon Whitear wrote:
> Jon Whitear wrote:
>
> > Hi,
> >
> > I'm running SVN7344. Live TV works fine on the first try, but if I
> > exit to the menu and go back in, I get a blank screen for ~20s and get
> > returned to the menu. If I keep trying, the backend dies.
Jon Whitear wrote:
Hi,
I'm running SVN7344. Live TV works fine on the first try, but if I
exit to the menu and go back in, I get a blank screen for ~20s and get
returned to the menu. If I keep trying, the backend dies.
I have attached logs from the frontend (-v network) and backend (-v
rec
13 matches
Mail list logo
