Noise crashes due to "Segmentation Fault"

Bug #1211512 reported by Alex
This bug report is a duplicate of:  Bug #1078284: Noise SIGSEGV. Edit Remove
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Noise
New
Undecided
Unassigned

Bug Description

Noise seems to randomly crash when listening to music (not happened so far without listening to music.
Running 'noise' in the terminal has given me this 'log': http://paste.ubuntu.com/5978706/
The last thing logged before crashing is 'Segmentation Fault' so I'm guessing it is due to this.
This is a recurring bug, it has happened every time between 30 seconds from the music start to about 15 minutes.

Noise 0.2

Tags: stability
Alex (ahtcx)
description: updated
Revision history for this message
Marcus Lundgren (marcus-lundgren) wrote :

Unfortunately, that log doesn't say much. As you say that this is an recurring bug for you, I would like you to do two things, and attach the outputs separately to this bug report. If you encounter any problems, or have any question, don't be afraid to ask!

Make sure that Noise is completely closed prior to the steps. You can do this running the following:

$ killall noise

*** 1. ***
In order to give better debug output, please start Noise using the following command in your terminal:

$ noise -d

Attach the output similarly as you did with your log.

*** 2. ***

(This step is based on this guide: https://wiki.debian.org/HowToGetABacktrace)

In order to actually pinpoint where it is happening, you'll have to start Noise using a command called gdb. But before we do this, we need to install some packages:

$ sudo apt-get install noise-dbg gdb

If no errors was shown, execute the following command:

$ gdb noise

When you see "(gdb)", you simply type the letter "r" and press enter. This will start Noise. When Noise crashes, you'll yet again see "(gdb)". Type in the two letters "bt", copy the output and attach the output to this bug.

If Noise is simply frozen when it has crashed, then press Ctrl+C in the terminal window. This will make you see the "(gdb)" in the terminal and then you can follow the instructions above (i.e. entering "bt").

Revision history for this message
Marcus Lundgren (marcus-lundgren) wrote :

Sorry, skip the first step.

In the second step, instead of just entering "r", type in "r -d" and copy everything that comes after that line (including the output that the "bt" step outputs) and attach that to this bug.

Revision history for this message
Alex (ahtcx) wrote :

Here is the output. Sorry I kind of screwed up the quitting bit, but it crashed on this bit: Program received signal SIGSEGV, Segmentation fault.

http://paste.ubuntu.com/5989221/

Revision history for this message
Alex (ahtcx) wrote :

Which I think makes it a duplicate of this bug? https://bugs.launchpad.net/noise/+bug/1176694

Revision history for this message
Marcus Lundgren (marcus-lundgren) wrote :

I am not sure that this is a duplicate of that bug, and since you now know how to extract meaningful logs, I'll open this again.

And you did unfortunately quit wrongly after you typed "bt", where you should have pressed the enter key instead until all of the trace was shown. Would mind redoing it, doing using the same steps as before?

Revision history for this message
Alex (ahtcx) wrote :

Oh OK, well I redid it, I think this was done properly. If not I can do it again.
http://paste.ubuntu.com/5990399/

Revision history for this message
Marcus Lundgren (marcus-lundgren) wrote :

You did everything correctly this time! Though, to fix the instances in the backtrace where it says "??" instead of a function name, I would like to install the following packages, which will reveal what the names really are:

sudo apt-get install libgtk-3-0-dbg libglib2.0-0-dbg libpango1.0-0-dbg

And then just redo what you did in your last log and attach the output as usual.

And I would also like to have some more information about when this is happening:

Does it happen only when Noise is switching to another song, in the middle of a song, or does it seem to be random?
Could it be a particular song that is triggering this? The reason I ask this is because the problem seems to happen in the container that holds the seekbar and music title in the toolbar.
Does it matter if the window is minimized or not?
Anything else that you've noticed when triggering this bug that might be of interest?

tags: added: stability
Revision history for this message
xapantu (xapantu) wrote :

I am not entirely sure about the duplicate, but the backtrace seems to be the same (hard to tell without the debug symbols). Please re-open if it is not fixed in recent updates.
Thanks for the report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.