latest beta bugs

[Dirk Hohndel]

> On Apr 12, 2020, at 12:17 PM, Berthold Stoeger <bstoeger at mail.tuwien.ac.at> wrote:
>> 
>> I assume that this is similar to what Berthold says he can reproduce.
> 
> Not sure, could be the same cause though:

The backtrace tells a very different story:

> Backtrace:
> 
> #3  0x00007ffff6c82c77 in QQmlData::destroyed(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
> #4  0x00007ffff5ed01ca in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #5  0x00007ffff70d1b1a in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
> #6  0x00007fffea677f21 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so
> #7  0x00007ffff5ec610e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #8  0x00007ffff5ed06ef in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #9  0x00007ffff70d1b1a in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
> #10 0x00007ffff70f3541 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
> #11 0x00007ffff5ec8c64 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #12 0x00007ffff70d001b in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
> #13 0x00007ffff75afa86 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
> #14 0x00007ffff75b8e00 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
> #15 0x00007ffff5e9ca2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #16 0x00007ffff5e9f6a8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #17 0x00007ffff5ef5037 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #18 0x00007ffff48488bd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #19 0x00007ffff4848b40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #20 0x00007ffff4848be3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #21 0x00007ffff5ef46b4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5

This is back to the crash that we have seen when working on the new dive list model.
After updating the notification text (triggered by saving the data file) we tell Qt to process pending events so that the user actually sees the notification.
And that then causes a crash as some QML element gets deleted and is deeply displeased about that.
The easy fix is to not call processEvents() -- which of course means that the user no longer gets updates

Sigh.

But no, this isn't the FullText crash that I can reproduce on my 32bit Android phone.

/D

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20200412/27f987c9/attachment-0001.html>