mscore --long-version dumps core

• Mar 22, 2017 - 07:00
Reported version
3.0
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

musescore --long-version (without some file parameter) dumps core:

musescore --long-version
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build 3426ac1
Segmentation fault (core dumped)

(Fedora 25)

Running with gdb:
(gdb) where
#0 0x00007fffef8d8f8d in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) ()
at /lib64/libQt5Core.so.5
#1 0x00007fffd866afb0 in QDBusConnectionPrivate::closeConnection() () at /lib64/libQt5DBus.so.5
#2 0x00007fffd8657852 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#3 0x00007fffef70e9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#4 0x00007ffff66836ca in start_thread () at /lib64/libpthread.so.0
#5 0x00007fffeee0af7f in clone () at /lib64/libc.so.6

Attachment Size
mscore.strace.txt 502.76 KB

Comments

• Mar 23, 2017 - 06:25
Status (old) active ⇒ duplicate

FYI, according to https://musescore.org/en/node/105731#comment-476446 this is the same stack trace I myself was getting in a year ago:

1	QObject::disconnect	qobject.cpp	2949	0x7fffef487ab7	
2	QObject::disconnect	qobject.h	361	0x7fffe011bf78	
3	QDBusConnectionPrivate::closeConnection	qdbusintegrator.cpp	1126	0x7fffe011bf78	
4	QDBusConnectionManager::run	qdbusconnection.cpp	191	0x7fffe010cb36	
5	QThreadPrivate::start	qthread_unix.cpp	340	0x7fffef283de8	
6	start_thread			0x7ffff480d424	
7	clone			0x7fffee987cbd

Reply

• Mar 23, 2017 - 06:51

From reading the associated QT bug report, it seems this issue might not be in Qt 5.8. Could you try upgrading your Qt install to Qt 5.8 (if it is not already) and report back if can run the infinite loop:

while true;
do
musescore --long-version;
done

without it outputting any segfaults?

Reply

• Mar 23, 2017 - 06:53

I think the problem is that mscore operates without file argument: I saw this problem already on mscore 2 if leaving mscore without having opened any file.

rpm -qa |grep qt5:

qtermwidget-qt5-0.6.0-4.fc24.x86_64
qt5-qttools-devel-5.7.1-4.fc25.x86_64
qt5-qtbase-mysql-5.7.1-14.fc25.x86_64
qt5-qtwebchannel-devel-5.7.1-2.fc25.x86_64
qt5-linguist-5.7.1-4.fc25.x86_64
qt5-qtwebchannel-5.7.1-2.fc25.x86_64
mingw64-qt5-qmldevtools-devel-5.6.0-2.fc25.x86_64
qt5-qtwebkit-devel-5.7.1-2.fc25.x86_64
qt5-qttools-libs-clucene-5.7.1-4.fc25.x86_64
qt5-qtwayland-5.7.1-2.fc25.x86_64
qt5-srpm-macros-5.7.1-1.fc25.noarch
qt5-qtquick1-5.7.1-1.2bc722agit.fc25.x86_64
qtermwidget-qt5-devel-0.6.0-4.fc24.x86_64
qt5-qttools-libs-help-5.7.1-4.fc25.x86_64
qt5-qtdeclarative-devel-5.7.1-5.fc25.x86_64
qt5-qtwebkit-5.7.1-2.fc25.x86_64
qt5-qtwebengine-doc-5.7.1-4.fc25.noarch
python-qt5-5.7-4.fc25.x86_64
qt5-qdoc-5.7.1-4.fc25.x86_64
qt5-qtbase-5.7.1-14.fc25.x86_64
qt5-qtbase-common-5.7.1-14.fc25.noarch
qt5-qtbase-devel-5.7.1-14.fc25.x86_64
qt5-qttools-libs-designer-5.7.1-4.fc25.x86_64
qt5-qtlocation-5.7.1-2.fc25.x86_64
qca-qt5-2.1.3-3.fc25.x86_64
qt5-qtscript-5.7.1-2.fc25.x86_64
qt5-qtquickcontrols-5.7.1-2.fc25.x86_64
libkscreen-qt5-5.8.6-1.fc25.x86_64
qt5-qtserialport-5.7.1-2.fc25.x86_64
poppler-qt5-devel-0.45.0-2.fc25.x86_64
qt5-qtscript-devel-5.7.1-2.fc25.x86_64
grantlee-qt5-5.1.0-2.fc25.x86_64
mingw64-qt5-qttools-tools-5.6.0-2.fc25.x86_64
qt5-qtwebengine-devel-5.7.1-4.fc25.x86_64
qt5-qtenginio-1.6.2-2.fc25.x86_64
python-qt5-webengine-5.7-4.fc25.x86_64
python3-qt5-webengine-5.7-4.fc25.x86_64
qt5-qtmultimedia-5.7.1-2.fc25.x86_64
qt5-qtbase-gui-5.7.1-14.fc25.x86_64
mingw64-qt5-qmldevtools-5.6.0-2.fc25.x86_64
qt5-qttools-common-5.7.1-4.fc25.noarch
qt5-rpm-macros-5.7.1-1.fc25.noarch
qt5-qtimageformats-5.7.1-2.fc25.x86_64
qt5-qhelpgenerator-5.7.1-4.fc25.x86_64
qt5-qtsvg-5.7.1-2.fc25.x86_64
qt5-qtxmlpatterns-5.7.1-4.fc25.x86_64
qt5-qdbusviewer-5.7.1-4.fc25.x86_64
qt5-qtwebsockets-5.7.1-2.fc25.x86_64
qt5-qttools-static-5.7.1-4.fc25.x86_64
qt5-qtconnectivity-5.7.1-2.fc25.x86_64
polkit-qt5-1-0.112.0-8.fc25.x86_64
poppler-qt5-0.45.0-2.fc25.x86_64
python3-qt5-5.7-4.fc25.x86_64
phonon-qt5-4.9.0-3.fc25.x86_64
adwaita-qt5-0.98-1.fc25.x86_64
qt5-qtdeclarative-5.7.1-5.fc25.x86_64
qt5-qtxmlpatterns-devel-5.7.1-4.fc25.x86_64
phonon-qt5-backend-gstreamer-4.9.0-1.fc25.x86_64
qt5-qtsvg-devel-5.7.1-2.fc25.x86_64
qt5-qttools-5.7.1-4.fc25.x86_64
qt5-qtquick1-devel-5.7.1-1.2bc722agit.fc25.x86_64
qt5-qttools-libs-designercomponents-5.7.1-4.fc25.x86_64
qt5-qtwebengine-examples-5.7.1-4.fc25.x86_64
qt5-designer-5.7.1-4.fc25.x86_64
python-qt5-rpm-macros-5.7-4.fc25.noarch
mingw64-qt5-qmake-5.6.0-4.fc25.x86_64
qt5-qtsensors-5.7.1-3.fc25.x86_64
dbusmenu-qt5-0.9.3-0.11.20150604.fc24.x86_64
mingw64-qt5-qtdeclarative-5.6.0-2.fc25.noarch
qt5-qtx11extras-5.7.1-2.fc25.x86_64
qt5-style-oxygen-5.8.6-1.fc25.x86_64
qt5-qtlocation-devel-5.7.1-2.fc25.x86_64
qt5-qtwebengine-5.7.1-4.fc25.x86_64
qt5-qtgraphicaleffects-5.7.1-2.fc25.x86_64
qt5-qtdoc-5.7.1-1.fc25.noarch
mingw64-qt5-qtbase-5.6.0-4.fc25.noarch

Reply

• Mar 23, 2017 - 06:54

Also before upgrading, I would be curious for you to try running the 3.0 Nighly linux AppImage in an infinite loop, since the 3.0 AppImages should be bundled with Qt 5.8 libs, I think.

Reply

• Mar 23, 2017 - 07:12

1. I'm building a new mscore-3 almost each morning by using the git source, so I think It's always up to date.

2. Fedora25 has no qt 5.8.

3. Running the shell loop lets mscore-3 crash at each mscore-3 call (this happens with the most recent git source too):

while true;do mscore --long-version;done
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
MuseScore: Music Score Editor
Unstable Prerelease for Version 3.0.0; Build d19dd40
Segmentation fault (core dumped)
...
...

Reply

• Mar 23, 2017 - 07:43

Well this is interesting that it happens *every* time for you. With me on Qt <5.8, it only happened *sporadically*.

I don't know if it has anything to do with "mscore operates without file argument: I saw this problem already on mscore 2 if leaving mscore without having opened any file". But as I said I don't know much about what is going on.

Anyway I think you *should* install Qt 5.8 if you are doing 3.0-dev work, because I believe the core devs decided that 3.0 is moving to Qt 5.8. You can download Qt 5.8 for linux from https://www.qt.io/download/ (make sure to select open source community version).

Reply

• Mar 23, 2017 - 13:49

1. Thank you, it works (MuseScoreNightly-201703222023-master-d19dd40-x86_64.AppImage). But: it is built with qt-5.6 and not with qt-5.8 as you assumed in comment #8. So why to install qt-5.8?

2. Running the appimage does not crash if called with the argument --long-version :-)

Reply

• Mar 23, 2017 - 14:38

It seems you are right about it being built with qt 5.6, according to this line . Strange. I'm sorry I assume and said it was built with 5.8. But anyway, this means that my conclusion that 5.8 was responsible for fixing the bug may have been misguided. So I can't explain at the moment why you are able to run the AppImage built with 5.6 just fine. Maybe they fixed the bug for 5.6 because 5.6 is a "Long Term Release", but then didn't fix it for 5.7.1 because 5.7.1 is not a long term release.

I'm going to keep #105731: Sporadic Crash on exit during callq in QObject::disconnect labeled as "won't fix" since it seems this bug is Qt's responsibility.

Reply