[mythtv-commits] Ticket #3836: MythMusic crashes when visualizers are changed repeatedly
MythTV
mythtv at cvs.mythtv.org
Sat Mar 8 09:17:16 UTC 2008
#3836: MythMusic crashes when visualizers are changed repeatedly
----------------------------------+-----------------------------------------
Reporter: otto at kolsi dot fi | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 0.22
Component: mythmusic | Version: head
Severity: medium | Resolution:
Mlocked: 0 |
----------------------------------+-----------------------------------------
Comment(by otto at kolsi dot fi):
After opening this ticket I've upgraded hardware and rebuilt a frontend
upgrading from FC5 -> FC8. With the new system it seems that none of the
Myth visualizers crash, only some of the libvisual visualizers. All the
others than those mentioned below seem to work fine even when 'tortured'
with repeated changes etc.
Some libvisual visualizers output errors before/during crash, e.g.:
'''nastyfft:'''
{{{
/usr/local/bin/mythfrontend: symbol lookup error:
/usr/lib/libvisual-0.4/actor/actor_nastyfft.so: undefined symbol:
visual_mem_malloc0
}}}
'''gdkpixbuff:'''
{{{
(process:5946): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion
`src != NULL' failed
libvisual CRITICAL: mythmusic: update_scaled_pixbuf(): assertion
`priv->scaled != NULL' failed
}}}
'''gforce:'''
{{{
libvisual CRITICAL: mythmusic: mfl_DestroyFont(): assertion `f != NULL'
failed
}}}
'''jess''' crashes and doesn't output anything. Backtrace of one of the
crashes is attached.
I think the original problem for me has either been solved by some
changeset or the system upgrade solved it. Can someone confirm from the
latest backtrace that the crash does not occur within MythMusic? And
finally, if libvisual component crashes, there is no point taking
backtraces since nothing can be done within MythMusic?
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/3836#comment:14>
MythTV <http://svn.mythtv.org/trac>
MythTV
More information about the mythtv-commits
mailing list