[PyQt] Qt 5.13: Segfault on exit with Windows + QtWebEngine

[BPL]

Florian,

Is this thread related to the other one I'd opened few days ago called
"QtWebEngine
crashing with certain app attributes
<https://www.riverbankcomputing.com/pipermail/pyqt/2019-July/041969.html>"?

Asking as that thread hadn't been replied at all but this seems to be
related (it also crashes on exit)... btw, I'd opened that thread here in
the pyqt mailing list
but I wanted to test it first on c++. Unfortunately for some reason
qtcreator wouldn't find qtwebengine (which I installed with
the maintenance tool on top of an existing qt installation):

untitled.pro:

QT += gui webenginewidgets

CONFIG += c++11 console
CONFIG -= app_bundle

DEFINES += QT_DEPRECATED_WARNINGS
SOURCES += main.cpp

# Default rules for deployment.
qnx: target.path = /tmp/$${TARGET}/bin
else: unix:!android: target.path = /opt/$${TARGET}/bin
!isEmpty(target.path): INSTALLS += target

main.cpp:

#include <QApplication>
#include <QtOpenGL/QtOpenGL>
#include <QtWidgets/QDockWidget>
#include <QtWidgets/QPlainTextEdit>

int main(int argc, char *argv[]) {
    bool MAKE_IT_CRASH = true;

    if (MAKE_IT_CRASH) {
        QCoreApplication::setAttribute(Qt::AA_UseOpenGLES);
    }

    QApplication a(argc, argv);

    QWebEngineView *view = new QWebEngineView(parent);
    view->load(QUrl("http://qt-project.org/"));
    view->show();

    return a.exec();
}

Probably this is a different issue but the fact you've said "you didn't Cc
the list" made me wonder if this could
be related somehow

On Tue, Jul 23, 2019 at 10:20 AM Florian Bruhin <me at the-compiler.org> wrote:

> Hi Phil,
>
> I assume you accidentally didn't Cc the list, so I added it back.
>
> On Sun, Jul 21, 2019 at 06:10:58PM +0100, Phil Thompson wrote:
> > In tonight's SIP and PyQt5 snapshots I have re-written how QObjects are
> > cleaned up when an application exits.
> >
> > Are you able to test these changes (from the source code)? There is no
> hurry
> > as I don't plan on making new releases until Qt 5.13.1.
> >
> > I'm a bit nervous about the changes as they could simply replace one set
> of
> > problems with another.
>
> The good news: This seems to fix a long-standing problem I have with
> QtWebEngine cookies not being saved on exit:
> https://github.com/qutebrowser/qutebrowser/issues/2263
>
> The bad news: You seem to be right. I only did a couple of quick tests on
> Linux, and so far I got:
>
> - An abort() due to an error in PyQtSlotProxy::unislot():
>   https://paste.the-compiler.org/view/8a17300b
>   (I don't have the error message I'm afraid)
>
> - An X error and assertion failure inside Chromium:
>   https://paste.the-compiler.org/view/b9219e33
>
> Florian
>
> --
> https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
>          I love long mails! | https://email.is-not-s.ms/
> _______________________________________________
> PyQt mailing list    PyQt at riverbankcomputing.com
> https://www.riverbankcomputing.com/mailman/listinfo/pyqt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20190723/45b06ecb/attachment.html>