Backtrace logs.........

General discussions
Locked
kinggo
Posts: 247
Joined: Thu Feb 09, 2012 5:54 am

Backtrace logs.........

Post by kinggo »

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff56c1e6c in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
(gdb) bt
#0 0x00007ffff56c1e6c in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#1 0x00007ffff56c2099 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2 0x00007ffff56a64fb in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3 0x00007ffff56bf41e in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4 0x00007ffff56be29d in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5 0x00007ffff56a8fa4 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#6 0x00007ffff56aa1d4 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7 0x00007ffff56aa221 in dbus_connection_flush ()
from /lib/x86_64-linux-gnu/libdbus-1.so.3
#8 0x00000000006dbbc9 in guMPRIS2::OnPlayerTrackChange (this=0x46c3880)
at /home/mario/guayadeque/src/dbus/mpris2.cpp:549
#9 0x00007ffff7b69ad6 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#10 0x00007ffff7b69e7f in wxEvtHandler::SearchDynamicEventTable(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#11 0x00007ffff7b69f32 in wxEvtHandler::ProcessEvent(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#12 0x00007ffff7b69a40 in wxEvtHandler::ProcessPendingEvents() ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#13 0x00007ffff7aec929 in wxAppConsole::ProcessPendingEvents() ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#14 0x00007ffff76f4369 in wxAppBase::ProcessIdle() ()
---Type to continue, or q to quit---
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#15 0x00007ffff766ebde in ?? ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#16 0x00007ffff608aab5 in g_main_context_dispatch ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff608ade8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff608b1e2 in g_main_loop_run ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff3362c77 in gtk_main ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#20 0x00007ffff7682088 in wxEventLoop::Run() ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#21 0x00007ffff76f416c in wxAppBase::MainLoop() ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#22 0x00007ffff7b1b6c5 in wxEntry(int&, wchar_t**) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#23 0x00000000004a09f2 in main (argc=1, argv=)
at /home/mario/guayadeque/src/MainApp.cpp:40
(gdb)
User avatar
anonbeat
Posts: 2048
Joined: Thu Sep 16, 2010 9:47 pm

Backtrace logs.........

Post by anonbeat »

This last two crashes happens in the same functions dbus_connection_flush

Looks like a dbus library problem

What are you using to control guayadeque via mpris ?
kinggo
Posts: 247
Joined: Thu Feb 09, 2012 5:54 am

Backtrace logs.........

Post by kinggo »

I have to say that I actually very rarely control anything. In most cases all I do is select a genre and hit shuffle, that's all. And when I do use controls then I use built in controls on my laptop (vostro 3500).
But I think that I found kind of pattern for segfaults. I can't reproduce them at will and maybe I just imagine things but I noticed that a lot of those segfaults happened after some longer period of playing while I wasn't doing anything else, there was something downloading sometimes but that's it. But then when I start to do something and CPU gets under some load I noticed that after currently playing song ends I get segfault. Not always but....... Maybe it's just coincidence.
And since I'm talking about CPU load, I noticed something else also. When I'm extracting some large archive or encoding some video and both CPU and hard drive are under heavy load guayadeque normally goes to a next song in the playlist and the progress bar (seekbar, playbar) moves but I have no sound output. At some point (10s, 20s, 30s) sound comes back and all is fine. It's like someone pressed mute button. I even manually changed the priority of pulse audio to very high but that doesn't help. The thing that helped to reduce this behavior a lot was disabling crossfading.
User avatar
anonbeat
Posts: 2048
Joined: Thu Sep 16, 2010 9:47 pm

Backtrace logs.........

Post by anonbeat »

I will not go into this as I think its a dbus library problem.
kinggo
Posts: 247
Joined: Thu Feb 09, 2012 5:54 am

Backtrace logs.........

Post by kinggo »

you said that you won't go into this, but..........
guayadeque was playing normally, and then it stopped at the and of the track. Actually, I think that that's the time when it is supposed to go on the next track because my fade-out is set at 5s.
http://i45.tinypic.com/10i7whl.jpg
Meanwhile I was encoding DTS to AC3 with avidemux and saving that video.
http://i49.tinypic.com/43lgg.jpg
And when this was done, guayadeque resumed playing the next song in the playlist but at the ~2:45 mark.
http://i47.tinypic.com/2mnjcpd.jpg
And in the meanwhile it was in the state as seen on first picture.

And I think it related to hard drive busyness 'cause I have the same behavior when I'm copying a couple of large files at once to external USB. Guayadeque stops and then resumes when copying is complete.
kinggo
Posts: 247
Joined: Thu Feb 09, 2012 5:54 am

Backtrace logs.........

Post by kinggo »

since I updated to 1871 this morning I had 3 segfaults already.
It's the same like it was prior to 1861 or so. I reported somewhere that it is OK. It was like a month ago. And since than I had only 1 segfault but today on 1871 I had 3.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe5512700 (LWP 4491)]
0x00007ffff56c1e77 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
(gdb) bt
#0 0x00007ffff56c1e77 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#1 0x00007ffff56c2099 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2 0x00007ffff56a64fb in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3 0x00007ffff56a8133 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4 0x00000000006d9287 in guMPRIS2::HandleMessages (this=0x4718360,
msg=, reply=0x7fffd8001a00)
at /home/mario/guayadeque/src/dbus/mpris2.cpp:1738
#5 0x00000000006d373d in guDBusServer::HandleMessages (this=0x472dce0,
msg=0x7fffd80019e0, reply=0x7fffd8001a00)
at /home/mario/guayadeque/src/dbus/gudbus.cpp:155
#6 0x00000000006d42c2 in Handle_Messages (conn=,
msg=0x7fffd80017e0, udata=0x472dce0)
at /home/mario/guayadeque/src/dbus/gudbus.cpp:35
#7 0x00007ffff56a9bde in dbus_connection_dispatch ()
from /lib/x86_64-linux-gnu/libdbus-1.so.3
#8 0x00007ffff56aa066 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#9 0x00000000006d368f in guDBusThread::Entry (this=0x471bee0)
at /home/mario/guayadeque/src/dbus/gudbus.cpp:585
#10 0x00007ffff7b689eb in wxThreadInternal::PthreadStart(wxThread*) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#11 0x00007ffff386fe9a in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007ffff3f93cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
---Type to continue, or q to quit---
#13 0x0000000000000000 in ?? ()
(gdb)
kinggo
Posts: 247
Joined: Thu Feb 09, 2012 5:54 am

Backtrace logs.........

Post by kinggo »

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe54f1700 (LWP 7654)]
0x00007fffd8009080 in ?? ()
(gdb) bt
#0 0x00007fffd8009080 in ?? ()
#1 0x00007ffff56a9bde in dbus_connection_dispatch ()
from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2 0x00007ffff56aa066 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3 0x00000000006d399f in guDBusThread::Entry (this=0x493aa20)
at /home/mario/guayadeque/src/dbus/gudbus.cpp:585
#4 0x00007ffff7b689eb in wxThreadInternal::PthreadStart(wxThread*) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5 0x00007ffff386fe9a in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#6 0x00007ffff3f93cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x0000000000000000 in ?? ()
(gdb)
kinggo
Posts: 247
Joined: Thu Feb 09, 2012 5:54 am

Backtrace logs.........

Post by kinggo »

ubuntu gnome 13.04 with shell 3.8

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffbd6a6700 (LWP 18788)]
0x00007fffc4000078 in ?? ()
(gdb) bt
#0 0x00007fffc4000078 in ?? ()
#1 0x00007fffcd5316ae in ?? ()
from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstflump3dec.so
#2 0x00007fffcd53175b in ?? ()
from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstflump3dec.so
#3 0x00007fffcd531814 in ?? ()
from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstflump3dec.so
#4 0x00007fffcd53755f in ?? ()
from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstflump3dec.so
#5 0x00007fffcd52f3e6 in ?? ()
from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstflump3dec.so
#6 0x00007fffcd530caf in ?? ()
from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstflump3dec.so
#7 0x00007ffff65e5db1 in gst_pad_push ()
from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
#8 0x00007fffe1e0c7ca in gst_base_parse_push_frame ()
from /usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0
#9 0x00007fffe1e0d80e in ?? ()
from /usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0
#10 0x00007fffe1e101a5 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0
#11 0x00007ffff660be34 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
---Type to continue, or q to quit---
#12 0x00007ffff60ab6f2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff60aaeb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff385df8e in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#15 0x00007ffff3f87e1d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)
User avatar
anonbeat
Posts: 2048
Joined: Thu Sep 16, 2010 9:47 pm

Backtrace logs.........

Post by anonbeat »

Looks like a gstreamer bug
kinggo
Posts: 247
Joined: Thu Feb 09, 2012 5:54 am

Backtrace logs.........

Post by kinggo »

well, very possible. There's a lot of updates every day and this happened only once so far.
Locked