Opened 13 years ago
Closed 11 years ago
#10075 closed Bug Report - Crash (Unverified)
Frontend abort on DVB playback start with Xv
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | major | Milestone: | 0.27 |
Component: | MythTV - Video Playback | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Attached backtrace show frontend abort/crash when DVB recording playback is started. This has only happened once or twice, and is not really reproducible. Backtrace shows execution within: VideoOutputXv::CreateShmImages?()
Git version is: c51b922b7b8f76ebf761d25580465c4666228cc2
Attachments (7)
Change History (18)
Changed 13 years ago by
Attachment: | playback-start-bt.txt added |
---|
Changed 13 years ago by
Attachment: | mfe-version.txt added |
---|
Changed 13 years ago by
Attachment: | mfe-playback-abort-log1.txt added |
---|
Changed 13 years ago by
Attachment: | playback-start-bt2.txt added |
---|
Changed 13 years ago by
Attachment: | mfe-playback-abort-log2.txt added |
---|
comment:2 Changed 13 years ago by
Otto - do you have the associated mythfrontend logs referenced in the bt? Might help shed some light on the root cause.
While the decoder thread (running CreateShmImages?) initially looks at fault (and the stack for that thread is similar to an X thread related crash), it looks as if it is actually the main thread that is aborting - std::terminate - but there is absolutely no hint as to why.
I've attached log related to the original abort. I've also attached second backtrace and associated log from another abort.
Couple of things to notice:
comment:3 follow-up: 4 Changed 13 years ago by
Can you post the full output of mythfrontend -v playback --loglevel=debug for a crash - and confirm what GPU and driver you are using?
A couple of things to test:-
- what happens if time stretch is disabled? (i.e. is at 1x)
- what happens if you comment out the disp->Sync() line in VideoOutputXv::CreateShmImages??
thanks, Mark
(p.s. looks like it is a crash in X, though that section of code is pretty heavily locked so I can't honestly see where the problem is)
Changed 13 years ago by
Attachment: | playback-start-bt3.txt added |
---|
Changed 13 years ago by
Attachment: | mfe-playback-abort-log3.txt added |
---|
comment:4 follow-up: 5 Changed 13 years ago by
Replying to markk:
Can you post the full output of mythfrontend -v playback --loglevel=debug for a crash - and confirm what GPU and driver you are using?
Attached new backtrace and corresponding log with debug log level. GPU is nVidia GeForce? 6200 and driver is nVidia's 260.19.36 (Fedora 13).
A couple of things to test:-
- what happens if time stretch is disabled? (i.e. is at 1x)
- what happens if you comment out the disp->Sync() line in VideoOutputXv::CreateShmImages??
With 1.3x time stretch, the problem occurs 4 times out of 5 with one particular file. When time stretch is disabled, problem goes away (tested 10 times).
Haven't yet tested the code change, I'll get back to that later.
comment:5 Changed 13 years ago by
A couple of things to test:-
- what happens if you comment out the disp->Sync() line in VideoOutputXv::CreateShmImages??
Commenting that line sort of helps. Out of 10 playback startups only 2 now aborts, so it's not really fixed with that..
comment:6 Changed 12 years ago by
Milestone: | unknown → 0.25 |
---|---|
Status: | new → accepted |
comment:7 Changed 12 years ago by
Owner: | markk deleted |
---|---|
Status: | accepted → assigned |
comment:8 Changed 12 years ago by
Milestone: | 0.25 → unknown |
---|---|
Status: | assigned → new |
comment:9 follow-up: 10 Changed 11 years ago by
Milestone: | unknown → 0.27 |
---|---|
Priority: | minor → major |
Status: | new → infoneeded_new |
Otto, can you still reproduce this issue?
There's not a great deal of interest in the community for maintaining the Xv code with the next-generation video renders - OpenGL and VDPAU (and vaapi) - being available. So I can't make any promises that this will be fixed if it's still an issue.
I'm setting a milestone of 0.27 because we are either able to fix it for that release, or we decide now it's never going to be fixed.
comment:10 Changed 11 years ago by
Replying to stuartm:
Otto, can you still reproduce this issue?
Haven't seen this for awhile after upgrading the distro (Fedora 15 -> 18). This should be closed as unverified/invalid.
comment:11 Changed 11 years ago by
Resolution: | → Unverified |
---|---|
Status: | infoneeded_new → closed |
Closed at submitter's request
Otto - do you have the associated mythfrontend logs referenced in the bt? Might help shed some light on the root cause.
While the decoder thread (running CreateShmImages?) initially looks at fault (and the stack for that thread is similar to an X thread related crash), it looks as if it is actually the main thread that is aborting - std::terminate - but there is absolutely no hint as to why.