Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[DONE] Double free error when closing Sayonara
Closing sayonara /var/crash/_usr_bin_sayonara
[code]ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Oct 16 22:12:37 2016
DistroRelease: Ubuntu 16.04
ExecutablePath: /usr/bin/sayonara
ExecutableTimestamp: 1476553608
ProcCmdline: sayonara
ProcCwd: /home/test
PATH=(custom, no user)
00400000-00a86000 r-xp 00000000 08:12 1184919 /usr/bin/sayonara
00c85000-00ca3000 r--p 00685000 08:12 1184919 /usr/bin/sayonara
00ca3000-00ca6000 rw-p 006a3000 08:12 1184919 /usr/bin/sayonara

Edit: Output shortened

[Edited on 16-10-2016 by Lucio Carreras]
I cannot do anything with the procmap. I need a stacktrace (also called backtrace). A stack trace contains the last called methods. I intentionally triggered a free error here. The stack trace looks like that:

*** stack smashing detected ***: ./bin/sayonara terminated

Here, I can see in which method the error appears. This is the same binary I sent you. If the stack trace does not indicate anything you have to use a debugging tool like gdb.

Your last stack trace was this:

*** Error in `sayonara\': double free or corruption (!prev): 0x00000000034ee510 ***
======= Backtrace: =========

This indicates that probably some string data was deleted twice. But it does not show where in the code this malfunction appears. There are approx 80.000 lines and maybe 3000 String usages. It\'s the needle in the haystack.

The stack trace I sent you tells me the function (a function has between 1 and 50 lines) where I have to look for the error. In this case the \'parse_image\' function which was called by the \'bus_state_changed\' function. But without the function I have no clue where to search. All I can do is a blind shot into the sky.

In a release build every function information gets lost. In a debug build every function is still available in a human-readable way. That\'s one reason the binary is so large.

But I guess, the debug build saves information where the source code is located at the system. So when I create a debug build for you, the source code is in my home directory and therefore not available on your system.

You can compile sayonara yourself by following these steps. It lasts about 5 minutes and user interaction is required for about 30 seconds.

sudo apt-get install git

git clone -b master sayonara-player

sudo apt-get install cmake pkg-config qt5-default qttools5-dev qttools5-dev-tools \\
libqt5core5a libqt5network5 libqt5sql5 libqt5sql5-sqlite libqt5xml5 libtag1-dev \\
libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev  libsqlite3-0 libmtp-dev \\
gstreamer1.0-plugins-base gstreamer1.0-plugins-good

cd sayonara-player
mkdir -p build && cd build
make -j8 (if 8 processor cores)
sudo make install

I guess this is the only way to find the error. If you want your original sayonara installation back, you need to reinstall it:

sudo apt-get install --reinstall sayonara

I was trying to reproduce like crazy and finally I could reproduce the error. But the stack trace is the same as yours. Currently, if have no clue how to debug this. But I\'ll find out.
Ok, I guess I found the error Smile Yippie!

You have enabled the accent free search. Others don\'t. And I obviously changed my habits and I do not search anymore. :lol:
The player does not crash if you start and close it. But if you searched for one term during a session then the player crashes. I will test on another machine tomorrow and if nothing crashes anymore I\'ll upload a new version.

Indeed, accent-free search is enabled.

…it sounds so un-related :lol:

Bravo !
I hope, this bug is away now?
Did not have much time to play these days…

…but after few hours yesterday, playing randomly, searching titles, going back and forth… no crash.

So it seems solved !

Forum Jump:

Users browsing this thread: 1 Guest(s)