Modify

Ticket #10483 (closed Bug Report - General: Unverified)

Opened 15 months ago

Last modified 12 months ago

mythtranscode crasshes when using --profile for lossless transcodes

Reported by: adeffs.mythtv@… Owned by: beirdo
Priority: minor Milestone: unknown
Component: MythTV - Mythtranscode Version: Master Head
Severity: medium Keywords: transcode
Cc: Ticket locked: no

Description

http://www.gossamer-threads.com/lists/mythtv/users/508044

this could occur for non-lossless transcodes, but that is all I have set up and care to use for my personal needs atm.

When running a Transcode job from within MythTV the job will segfault. Upon attempting from the commandline using the command shown in the backendlog I get said segfault as well. I've run a backtrace, I will attach apport crash report(s if multiple are needed?) when I get home and can easily upload the file.

Attachments

gdb.txt (651 bytes) - added by Steven Adeff <adeffs.mythtv@…> 15 months ago.
gdb of a different run
mythtranscode.log (10.4 KB) - added by Steven Adeff <adeffs.mythtv@…> 15 months ago.
transcode log of said run

Change History

comment:1 Changed 15 months ago by Steven Adeff <adeffs.mythtv@…>

tincanfury.dyndns.org/users/tincanfury/_usr_bin_mythtranscode.107.crash.gz

too large to attach

comment:2 Changed 15 months ago by beirdo

  • Component changed from MythTV - General to MythTV - Mythtranscode

comment:3 Changed 15 months ago by beirdo

  • Owner set to beirdo
  • Status changed from new to assigned

comment:4 Changed 15 months ago by adeffs.mythtv@…

from apport, as per the wiki

https://bugs.launchpad.net/mythbuntu/+bug/962353

if that doesn't work for the devs I can create an "old school" gdb grab.

comment:5 Changed 15 months ago by Steven Adeff <adeffs.mythtv@…>

From the command line:

$ sudo -H -u mythtv /usr/bin/mythtranscode -j 119 --profile autodetect --honorcutlist --verbose most --loglevel info --syslog local7
2012-03-22 12:44:44.779928 C  mythtranscode version: master [v0.25-rc-26-g495ef16] www.mythtv.org
2012-03-22 12:44:44.779969 N  Enabled verbose msgs: most
2012-03-22 12:44:44.780008 N  Setting Log Level to LOG_INFO
2012-03-22 12:44:44.780099 I  Added logging to the console
2012-03-22 12:44:44.780137 I  Added syslogging to facility local7
2012-03-22 12:44:44.780148 I  Added database logging to table logging
2012-03-22 12:44:44.780245 N  Setting up SIGHUP handler
2012-03-22 12:44:44.780422 N  Using runtime prefix = /usr
2012-03-22 12:44:44.780459 N  Using configuration directory = /home/mythtv/.mythtv
2012-03-22 12:44:44.780611 E  (old)Settings::ReadSettings(settings.txt) - No such file settings.txt
2012-03-22 12:44:44.780723 I  Assumed character encoding: en_US.UTF-8
2012-03-22 12:44:44.781257 E  (old)Settings::ReadSettings(settings.txt) - No such file settings.txt
2012-03-22 12:44:44.781286 E  (old)Settings::ReadSettings(/usr/share/mythtv/mysql.txt) - No such file /usr/share/mythtv/mysql.txt
2012-03-22 12:44:44.781303 E  (old)Settings::ReadSettings(/usr/etc/mythtv/mysql.txt) - No such file /usr/etc/mythtv/mysql.txt
2012-03-22 12:44:44.781536 E  (old)Settings::ReadSettings(./mysql.txt) - No such file ./mysql.txt
2012-03-22 12:44:44.781582 I  Using localhost value of mythbackend
2012-03-22 12:44:44.781803 I  DefaultUPnP() - No default UPnP backend
2012-03-22 12:44:44.781819 I  Testing network connectivity to '192.168.1.151'
2012-03-22 12:44:44.782035 I  Starting process manager
2012-03-22 12:44:44.782096 I  Starting process signal handler
2012-03-22 12:44:44.784037 I  Managed child (PID: 26062) has started! * command=ping -t 3 -c 1  192.168.1.151  >/dev/null 2>&1, timeout=0
2012-03-22 12:44:44.784190 I  Starting IO manager (write)
2012-03-22 12:44:44.784204 I  Starting IO manager (read)
Segmentation fault (core dumped)

mythtranscode.log

Mar 22 12:44:44 mythbackend mythtranscode[26055]: C thread_unknown mythcommandli
neparser.cpp:2534 (ConfigureLogging) mythtranscode version: master [v0.25-rc-26-
g495ef16] www.mythtv.org
Mar 22 12:44:44 mythbackend mythtranscode[26055]: N thread_unknown mythcommandli
neparser.cpp:2536 (ConfigureLogging) Enabled verbose msgs: most
Mar 22 12:44:44 mythbackend mythtranscode[26055]: N thread_unknown logging.cpp:1
170 (logStart) Setting Log Level to LOG_INFO
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I thread_unknown logging.cpp:2
29 (FileLogger) Added logging to the console
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I thread_unknown logging.cpp:3
69 (SyslogLogger) Added syslogging to facility local7
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I thread_unknown logging.cpp:4
25 (DatabaseLogger) Added database logging to table logging
Mar 22 12:44:44 mythbackend mythtranscode[26055]: N thread_unknown logging.cpp:1
209 (logStart) Setting up SIGHUP handler
Mar 22 12:44:44 mythbackend mythtranscode[26055]: N thread_unknown mythdirs.cpp:
51 (InitializeMythDirs) Using runtime prefix = /usr
Mar 22 12:44:44 mythbackend mythtranscode[26055]: N thread_unknown mythdirs.cpp:
64 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Mar 22 12:44:44 mythbackend mythtranscode[26055]: E thread_unknown oldsettings.c
pp:128 (ReadSettings) (old)Settings::ReadSettings(settings.txt) - No such file s
ettings.txt
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I CoreContext mythcorecontext.
cpp:226 (Init) Assumed character encoding: en_US.UTF-8
Mar 22 12:44:44 mythbackend mythtranscode[26055]: E CoreContext oldsettings.cpp:
128 (ReadSettings) (old)Settings::ReadSettings(settings.txt) - No such file sett
ings.txt
Mar 22 12:44:44 mythbackend mythtranscode[26055]: E CoreContext oldsettings.cpp:
128 (ReadSettings) (old)Settings::ReadSettings(/usr/share/mythtv/mysql.txt) - No
 such file /usr/share/mythtv/mysql.txt
Mar 22 12:44:44 mythbackend mythtranscode[26055]: E CoreContext oldsettings.cpp:
128 (ReadSettings) (old)Settings::ReadSettings(/usr/etc/mythtv/mysql.txt) - No s
uch file /usr/etc/mythtv/mysql.txt
Mar 22 12:44:44 mythbackend mythtranscode[26055]: E CoreContext oldsettings.cpp:
128 (ReadSettings) (old)Settings::ReadSettings(./mysql.txt) - No such file ./mys
ql.txt
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I CoreContext mythcontext.cpp:
481 (LoadDatabaseSettings) Using localhost value of mythbackend
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I CoreContext mythcontext.cpp:
815 (DefaultUPnP) DefaultUPnP() - No default UPnP backend
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I CoreContext mythcontext.cpp:
608 (TestDBconnection) Testing network connectivity to '192.168.1.151'
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I SystemManager system-unix.cp
p:263 (run) Starting process manager
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I SystemSignalManager system-u
nix.cpp:485 (run) Starting process signal handler
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I CoreContext system-unix.cpp:
735 (Fork) Managed child (PID: 26062) has started! * command=ping -t 3 -c 1  192
.168.1.151  >/dev/null 2>&1, timeout=0
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I SystemIOHandlerW system-unix
.cpp:90 (run) Starting IO manager (write)
Mar 22 12:44:44 mythbackend mythtranscode[26055]: I SystemIOHandlerR system-unix
.cpp:90 (run) Starting IO manager (read)

Changed 15 months ago by Steven Adeff <adeffs.mythtv@…>

gdb of a different run

Changed 15 months ago by Steven Adeff <adeffs.mythtv@…>

transcode log of said run

comment:6 Changed 15 months ago by Steven Adeff <adeffs.mythtv@…>

I've attempted a gdb run of a transcode job, don't know if it will have any better information though?

comment:7 Changed 15 months ago by beirdo

Umm, when using gdb, we actually need a backtrace.

thread apply all bt full

Also, this is dying with qFatal. That means that Qt sent a fatal error message to the console where this was started, and that message is critical to figuring out what it didn't like. If you ran this from the prompt, what were the last few lines after the console logging?

comment:8 Changed 15 months ago by beirdo

At least that's what it seems from the wee gdb output.

comment:9 Changed 15 months ago by Steven Adeff <adeffs.mythtv@…>

This seems to have been fixed, though only for the master backend, at least in my system. I still have a few recordings that error, but not for this reason. I'll open another ticket for that issue.

comment:10 Changed 12 months ago by beirdo

  • Status changed from assigned to closed
  • Resolution set to Unverified

Closing at user request.

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.