Opened 12 years ago

Closed 12 years ago

#4238 closed defect (invalid)

blootube-wide & video settings: unknown tag image crashes frontend

Reported by: ikke@… Owned by: Justin Hornsby
Priority: minor Milestone: unknown
Component: theme Version: head
Severity: high Keywords:
Cc: Ticket locked: no

Description

I have experienced this problem with couple versions of trunk with few weeks difference. System is Ubuntu Gutsy. This happens while trying to enter into video settings (I guess video-plugin) from settings menu. Gui freezes for minutes, and then mythtvfrontend crashes.

Here's the latest log trace:

$ mythfrontend -d X Error: BadDevice?, invalid or uninitialized input device 171

Major opcode: 149 Minor opcode: 3 Resource id: 0x0

Failed to open device X Error: BadDevice?, invalid or uninitialized input device 171

Major opcode: 149 Minor opcode: 3 Resource id: 0x0

Failed to open device 2007-11-25 17:19:56.367 Using runtime prefix = /usr/local 2007-11-25 17:19:57.230 XScreenSaver support enabled 2007-11-25 17:19:57.230 DPMS is active. 2007-11-25 17:19:57.281 Empty LocalHostName?. 2007-11-25 17:19:57.281 Using localhost value of loota 2007-11-25 17:19:57.281 Testing network connectivity to 192.168.1.2 2007-11-25 17:19:57.371 New DB connection, total: 1 2007-11-25 17:20:02.425 Connected to database 'mythconverg' at host: 192.168.117.2 2007-11-25 17:20:02.427 Total desktop dim: 1920x1080, with 1 screen[s]. 2007-11-25 17:20:02.432 Using screen 0, 1920x1080 at 0,0 2007-11-25 17:20:02.486 Current Schema Version: 1201 2007-11-25 17:20:02.487 mythfrontend version: 0.21.20071123-1 www.mythtv.org 2007-11-25 17:20:02.488 Enabled verbose msgs: important general 2007-11-25 17:20:03.585 Total desktop dim: 1920x1080, with 1 screen[s]. 2007-11-25 17:20:03.588 Using screen 0, 1920x1080 at 0,0 2007-11-25 17:20:03.591 Switching to wide mode (blootube-wide) 2007-11-25 17:20:03.727 Using the Qt painter 2007-11-25 17:20:05.232 lirc init success using configuration file: /home/xxx/.mythtv/lircrc 2007-11-25 17:22:07.926 Loading from: /usr/local/share/mythtv/themes/blootube-wide/base.xml 2007-11-25 17:22:07.945 Loading from: /usr/local/share/mythtv/themes/default/base.xml 2007-11-25 17:22:08.077 Key W is bound to multiple actions in context TV Playback. 2007-11-25 17:22:08.194 Registering Internal as a media playback plugin. 2007-11-25 17:22:08.405 MonitorRegisterExtensions?(0x100, gif,jpg,png) 2007-11-25 17:22:08.830 MonitorRegisterExtensions?(0x40, ogg,mp3,aac,flac) 2007-11-25 17:22:08.961 Connecting to backend server: 192.168.1.2:6543 (try 1 of 5) 2007-11-25 17:22:08.963 Using protocol version 36 2007-11-25 17:22:08.976 Starting media monitor. 2007-11-25 17:22:08.979 NetworkControl?: Listening for remote connections on port 6546 2007-11-25 17:22:09.025 MythThemedMenuPrivate?: Unknown tag image in background 2007-11-25 17:22:14.795 Detected MediaType? MEDIATYPE_DVD 2007-11-25 17:22:14.797 Media status changed... (MEDIATYPE_DVD, MEDIASTAT_NOTMOUNTED -> MEDIASTAT_USEABLE) 2007-11-25 17:24:25.117 New DB connection, total: 2 2007-11-25 17:24:30.145 Connected to database 'mythconverg' at host: 192.168.117.2 2007-11-25 17:24:33.169 XMLParse::LoadTheme? using /usr/local/share/mythtv/themes/blootube-wide/video-ui.xml 2007-11-25 17:24:34.217 Unable to find image file: /usr/local/share/mythtv/themes/blootube-wide/trans-mv-mselect.png 2007-11-25 17:24:34.217 UIImageType::LoadImage?() - Cannot find image: trans-mv-mselect.png 2007-11-25 17:24:45.935 MythThemedMenuPrivate?: Unknown tag image in background Killed

Change History (3)

comment:1 Changed 12 years ago by ikke@…

I don't know why I can't get backtrace. I did svn update, compiled with --compile-type=debug, installed. Both for mythtv and mythplugins trunk. Then restarted backend, followed the instructions in myth manual to take backtrace with gdb, also by giving the commands within gdb, but still I don't get trace! WTF?

gdb.txt: " Starting program: /usr/local/bin/mythfrontend [Thread debugging using libthread_db enabled] [New Thread -1255392480 (LWP 2330)] [New Thread -1257768048 (LWP 2336)] [New Thread -1266160752 (LWP 2337)] [New Thread -1274553456 (LWP 2338)] [New Thread -1285715056 (LWP 2343)] [New Thread -1313809520 (LWP 2344)] [New Thread -1341473904 (LWP 2349)] [New Thread -1349866608 (LWP 2350)] [New Thread -1358259312 (LWP 2351)]

Program terminated with signal SIGKILL, Killed. The program no longer exists. No stack. "

comment:2 Changed 12 years ago by ikke@…

ok, like Aaron adviced me, it was kernel that kills memory hungry beasts. It seems 1 GB is not enough for the theme ;)

Just tell me what more you want me to trace this one... it seems to be randow sw which gets killed by oom-killer, but it gets triggered always by going to this utilities/setup-> setup -> media -> video settings with blootube-wide. The other theme (neon-wide) doesn't do this.

comment:3 Changed 12 years ago by stuartm

Resolution: invalid
Status: newclosed

Entering the plugin menus causes the images used for that plugin to be loaded (even if they are already loaded for use in mythfrontend). I've a task ticket open for this issue and it would be solved by moving the existing image "cache" to become a global cache covering all plugins loaded by mythfrontend.

Most likely the reason Blootube-Wide causes problems but Neon doesn't, is because it uses larger images which consume more memory.

I'm going to close this, since there is a ticket open already and the crash described here isn't caused directly by mythtv but by the kernel.

Note: See TracTickets for help on using tickets.