Segmentation fault on playback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Jokosher |
Fix Released
|
High
|
Laszlo Pandy |
Bug Description
After creating a new project the following sequences caused the application to exit and 'Segmentation fault' to appear in the terminal:
- add instrument, record, play,
- add instrument, record, play, play,
- add instrument, record, play, record, play,
- add instrument, record, add instrument, record, play.
They sometimes go off, and sometimes they don't.
System:
Ubuntu Hardy, Linux kernel 2.6.24-19-generic
Device:
Intel 82801CA-ICH3
Backtrace:
#0 0x080f3ec0 in _PyObject_GC_Resize (op=0x8eda3cc, nitems=4)
at ../Modules/
#1 0x08112c68 in PyFrame_New (tstate=0x816b1b8, code=0x861e800,
globals=
#2 0x080c968b in PyEval_EvalFrameEx (f=0x8eded24, throwflag=0)
at ../Python/
#3 0x080cb1f7 in PyEval_EvalCodeEx (co=0x8596d58, globals=0x859157c,
locals=0x0, args=0x8b7b3a8, argcount=3, kws=0x0, kwcount=0, defs=0x0,
defcount=0, closure=0x0) at ../Python/
#4 0x0811372e in function_call (func=0x86d6764, arg=0x8b7b39c, kw=0x0)
at ../Objects/
#5 0x0805cb97 in PyObject_Call (func=0x8eda3cc, arg=0x8b7b39c, kw=0x0)
at ../Objects/
#6 0x08062bfb in instancemethod_call (func=0x86d6764, arg=0x8b7b39c, kw=0x0)
at ../Objects/
#7 0x0805cb97 in PyObject_Call (func=0x8eda3cc, arg=0x8bd04cc, kw=0x0)
at ../Objects/
#8 0x080c2e9c in PyEval_
arg=0x8bd04cc, kw=0x0) at ../Python/
#9 0x0805d040 in PyObject_CallObject (o=0x8bc8cd4, a=0x8bd04cc)
at ../Objects/
#10 0xb7d23afb in ?? ()
from /var/lib/
---Type <return> to continue, or q <return> to quit---
#11 0xb7cc6759 in g_closure_invoke () from /usr/lib/
#12 0xb7cdaf8b in ?? () from /usr/lib/
#13 0xb7cdcc1f in g_signal_
#14 0xb7cdcf69 in g_signal_emit () from /usr/lib/
#15 0xb6d0c3e7 in gst_bus_
data=0x0) at gstbus.c:1059
#16 0xb6d0d0bf in gst_bus_
callback=
at gstbus.c:779
#17 0xb7c34dd6 in g_main_
#18 0xb7c38193 in ?? () from /usr/lib/
#19 0xb7c38577 in g_main_loop_run () from /usr/lib/
#20 0xb77a9264 in gtk_main () from /usr/lib/
#21 0xb7b28ee0 in ?? ()
from /var/lib/
#22 0x080ca5c6 in PyEval_EvalFrameEx (f=0x817757c, throwflag=0)
at ../Python/
#23 0x080cb1f7 in PyEval_EvalCodeEx (co=0xb7dc58d8, globals=0xb7e16acc,
locals=
defcount=0, closure=0x0) at ../Python/
#24 0x080cb347 in PyEval_EvalCode (co=0xb7dc58d8, globals=0xb7e16acc,
locals=
#25 0x080ea818 in PyRun_FileExFlags (fp=0x816b008,
---Type <return> to continue, or q <return> to quit---
filename=
locals=
at ../Python/
#26 0x080eaab9 in PyRun_SimpleFil
filename=
at ../Python/
#27 0x08059335 in Py_Main (argc=1, argv=0xbffc5584) at ../Modules/
#28 0x080587f2 in main (argc=1, argv=0x0) at ../Modules/
This really needs a stacktrace to be useful. Is the bug reproducible every time?