Opened 12 years ago
Closed 11 years ago
#10875 closed Bug Report - Crash (Works for me)
AirPlay video playback causes MythFrontend to segfault
Reported by: | Owned by: | JYA | |
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | MythTV - Video Playback | Version: | Unspecified |
Severity: | medium | Keywords: | airplay |
Cc: | Ticket locked: | no |
Description
I am running Mythbuntu 12.04 with MythTV v0.25.1-49-g65913e7. I am attempting to playing video from an iPhone 4 with iOS 5.1.1 (9B206) on Verizon.
I have MYTHTV_AIRPLAY set and can play video fine through AirPlay? if initiated from the YouTube? app. However, when I attempt to play a video I recorded from my "Camera Roll" in the Photos app, it causes MythTV to segfault. Near as I can tell this is related to not being able to decode QuickTime?/MOV files but I haven't been able to find any documentation on how to enable that, and it seems like it shouldn't cause a segfault regardless.
To recreate the issue, I start /usr/bin/mythfrontend from the command line (with "export MYTHTV_AIRPLAY=1" already set in my .profile). I leave MythTV on the main menu. Then, on my iPhone, I go to "Camera Roll" and select a video to play. I can see my MythTV system as an output location from my iPhone, and choose it. The iPhone says it is playing through AirPlay?, but the MythTV frontend hangs and eventually crashes after about 10 seconds.
I'm attaching three files (1) the console output from when I was running mythfrontend until the segfault occurred, (2) the log in /var/log/mythtv/mythfrontend.log for the same time period, which is similar but not exactly the same, and (3) the output of mythfrontend --version.
Attachments (8)
Change History (23)
Changed 12 years ago by
Attachment: | mythfrontend--version.txt added |
---|
Changed 12 years ago by
Attachment: | mythfrontend.console.log added |
---|
Changed 12 years ago by
Attachment: | mythfrontend.log added |
---|
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Owner: | set to JYA |
---|---|
Status: | new → assigned |
Please attach the full backtrace of the coredump created. (as in thread apply all bt full)
comment:3 Changed 12 years ago by
Status: | assigned → infoneeded |
---|
comment:4 Changed 12 years ago by
Resolution: | → Works for me |
---|---|
Status: | infoneeded → closed |
no further info provided, and it works fine for me
Changed 12 years ago by
Attachment: | sample_sorenson.mov added |
---|
MythTV will crash if this file is played after playing sample.3gp
comment:5 Changed 12 years ago by
Resolution: | Works for me |
---|---|
Status: | closed → new |
I've attached three files:
mythfrontend_gdb.log.zip: This is the output from GDB from startup to the crash with a backtrace. I'm running Mythbuntu and just updated 8/18/2012 7am EDT. Version information is in the log. The backtrace has whatever symbol information is provided in the binary from the Mythbuntu distribution.
sample.3gp: After startup, I attempted to play this file through AirPlay? first. It didn't crash, but it failed to play. The frontend's log shows repeated attempts to play it.
sample_sorenson.mov: Attempting to play this file after sample.3gp results in the crash.
Note that other types of video files play fine. Please let me know if you need more information.
comment:6 Changed 12 years ago by
Status: | new → infoneeded_new |
---|
Provide a backtrace using master/0.26
This code is no longer relevant in 0.26
comment:10 Changed 12 years ago by
Resolution: | → Works for me |
---|---|
Status: | infoneeded_new → closed |
comment:11 Changed 12 years ago by
I have the same exact problem using 0.26 on a 12.04 Mythbuntu system (upgraded to latest mythfrontend in the PPA).
Changed 12 years ago by
Attachment: | mythfrontend_0.26_gdb-immediate crash.log added |
---|
Crashes immediately
Changed 12 years ago by
Attachment: | mythfrontend_0.26_gdb-pause then crash.log added |
---|
Pauses then crashes
comment:13 Changed 12 years ago by
There seem to be three different failure modes, all with the same file.
- Sometimes the frontend doesn't log any connection at all
- Sometimes the frontend crashes immediately
- Sometimes the frontend pauses before crashing. This one at least logs some info about not having the proper decoder.
I have attached the logs of running mythfrontend.real from startup to segfault for 2 & 3. The file I am using is 174MB; if it would be helpful I can try to create a file small enough to upload that still triggers the segfault.
Please let me know if there's any other information I can provide. I really appreciate your work.
comment:14 Changed 12 years ago by
Resolution: | Works for me |
---|---|
Status: | closed → new |
did you install the debugging symbols? the backtrace is very incomplete..
comment:15 Changed 11 years ago by
Resolution: | → Works for me |
---|---|
Status: | new → closed |
I also noticed the following in dmesg:
[ 672.751310] mythfrontend.re[3047]: segfault at 128c ip 00007f02cec2ff17 sp 00007fff2d0ccfa8 error 4 in libmythtv-0.25.so.0.25.0[7f02ce7a5000+944000]