[Interest] Crashing in qMetaTypeCustomType_unlocked

Thu Jul 9 21:51:26 CEST 2020

Just to bring this back to life (as we still have not been able to
track down the culprit)

#0  0x00007f162f9b0aa8 in qMetaTypeCustomType_unlocked(char const*,
int, int*) [clone .constprop.878] () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#1  0x00007f162f9b15f7 in qMetaTypeTypeInternal(char const*) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#2  0x00007f162f9a80de in
QMetaObjectPrivate::decodeMethodSignature(char const*,
QVarLengthArray<QArgumentType, 10>&) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#3  0x00007f162f9ae748 in QMetaObject::indexOfMethod(char const*)
const () from /opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#4  0x00007f1629d03fda in QDBusConnectionPrivate::findSlot(QObject*,
QByteArray const&, QVector<int>&) ()
   from /opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/plugins/bearer/../../lib/libQt5DBus.so.5
#5  0x00007f1629d047a0 in
QDBusConnectionPrivate::prepareHook(QDBusConnectionPrivate::SignalHook&,
QString&, QString const&, QString const&, QString const&, QString
const&, QStringList const&, QObject*, char const*, int, bool) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/plugins/bearer/../../lib/libQt5DBus.so.5
#6  0x00007f1629d050f1 in
QDBusConnectionPrivate::disconnectRelay(QString const&, QString
const&, QString const&, QDBusAbstractInterface*, QMetaMethod const&)
()
   from /opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/plugins/bearer/../../lib/libQt5DBus.so.5
#7  0x00007f1629d1685f in
QDBusAbstractInterfacePrivate::finishDisconnectNotify(QDBusAbstractInterface*,
int) ()
   from /opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/plugins/bearer/../../lib/libQt5DBus.so.5
#8  0x00007f162f9cad61 in QObject::event(QEvent*) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#9  0x00007f162f99e333 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#10 0x00007f162f9a0de7 in
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
() from /opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#11 0x00007f162f9f6123 in postEventSourceDispatch(_GSource*, int
(*)(void*), void*) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#12 0x00007f162ae70417 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f162ae70650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f162ae706dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f162f9f575f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#16 0x00007f162f99cc0a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#17 0x00007f162f7cdb6c in QThread::exec() () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#18 0x00007f162f7cf0a3 in QThreadPrivate::start(void*) () from
/opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/lib/libQt5Core.so.5
#19 0x00007f162d9996db in start_thread (arg=0x7f162a9a9700) at
pthread_create.c:463
#20 0x00007f162eeb888f in gnu_dev_makedev (__major=<optimized out>,
__minor=<optimized out>) at makedev.c:30
#21 0x0000000000000000 in ?? ()

That is the latest backtrace from a core dump. The Qt Libraries are
the Release versions so there are no symbols to get values for
unfortunately.

We have tried moving the plugins/bearer to the side but still get a crash.

Any more thoughts?
_________________________________________________________
Mike Jackson

On Mon, Jun 22, 2020 at 1:43 PM Michael Jackson
<mike.jackson at bluequartz.net> wrote:
>
> On 6/22/20, 1:20 PM, "Interest on behalf of Thiago Macieira" <interest-bounces at qt-project.org on behalf of thiago.macieira at intel.com> wrote:
>
>     On Monday, 22 June 2020 09:50:20 PDT Michael Jackson wrote:
>     > We are currently experiencing some intermittent crashing in our program. The
>     > stacktrace is below. The code was compiled in "Release" mode. This is on an
>     > Ubuntu 18.04 (with all updates) and using GCC 8.4.0
>     > (https://my.cdash.org/buildSummary.php?buildid=1843613). We use the
>     > prebuilt Qt 5.12.8 from the downloads.qt.io website. We are trying to
>     > reproduce the bug in a Debug build but no luck so far.
>     >
>     > I've never really had an issue like this and so I'm just looking for ideas
>     > on what it might be? Also note that we build nightly on macOS and Windows
>     > and those builds do not have any issues. Most use the same version of Qt
>     > 5.12.
>
>     Because those are probably not using D-Bus for anything. This is also showing
>     "plugins/bearer/../.." which is really weird. I've never seen this show up. I
>     don't know if we can attribute this to the NetworkManager bearer plugin (which
>     does use D-Bus) or if this is just a red herring.
>
>     But there's a simple way to test: can you delete the NM plugin and see if the
>     problem goes away?
>      plugins/bearer/*
>
>     --
>     Thiago Macieira - thiago.macieira (AT) intel.com
>       Software Architect - Intel System Software Products
>
>
> Thank you for the suggestion. I did the following (Hoping I interpreted your instructions correctly)
>
> $ cd /opt/DREAM3D_SDK/Qt5.12.8/5.12.8/gcc_64/plugins/bearer
> $ mv libqnmbearer.so bak_libqnmbearer.so.bak
>
> Kicked off a new build. Results will be at <https://dev.azure.com/BlueQuartzSoftware/DREAM3D/_build/results?buildId=279&view=logs&j=1ee29c43-a44e-5e49-79a9-6f3da8136d88>.
>
> --
> Michael Jackson
> BlueQuartz Software
> [e] mike.jackson at bluequartz.net
> [w] www.bluequartz.net
>
>
>