Bug#805265: libqt5network5: Sporadic segfault on exit in QNetworkConfigurationManagerPrivate::pollEngines()

[Florian Bruhin <me@the-compiler.org>]

Package: libqt5network5
Version: 5.3.2+dfsg-4+deb8u1
Severity: normal
Tags: upstream patch

Dear Maintainer,

I'm running a (Py)Qt5 application as part of a CI, and once all few days I get
a segfault on exit here:

	.../libQt5Network.so.5(QNetworkConfigurationManagerPrivate::pollEngines() 0xe4)[0x7f262566b9b4]
	.../libQt5Network.so.5( 0x10f20d)[0x7f26256db20d]
	.../libQt5Core.so.5(QMetaObject::activate(QObject*, int, int, void**) 0x77d)[0x7f262eb0ffdd]
	.../libQt5Core.so.5(QTimer::timerEvent(QTimerEvent*) 0x28)[0x7f262eb1da58]
	.../libQt5Core.so.5(QObject::event(QEvent*) 0xb3)[0x7f262eb10e93]
	.../libQt5Widgets.so.5(QApplicationPrivate::notify_helper(QObject*, QEvent*) 0x8c)[0x7f262758b12c]
	.../libQt5Widgets.so.5(QApplication::notify(QObject*, QEvent*) 0x3a0)[0x7f2627590600]
	.../QtWidgets.cpython-34m-x86_64-linux-gnu.so( 0x15f5b6)[0x7f26267d25b6]
	.../libQt5Core.so.5(QCoreApplication::notifyInternal(QObject*, QEvent*) 0xdb)[0x7f262eae0dcb]
	.../libQt5Core.so.5(QTimerInfoList::activateTimers() 0x595)[0x7f262eb38045]
	.../libQt5Core.so.5( 0x3314c1)[0x7f262eb384c1]
	.../libglib-2.0.so.0(g_main_context_dispatch 0x24d)[0x7f262daa6c5d]
	.../libglib-2.0.so.0( 0x49f48)[0x7f262daa6f48]
	.../libglib-2.0.so.0(g_main_context_iteration 0x2c)[0x7f262daa6ffc]
	.../libQt5Core.so.5(QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) 0x6c)[0x7f262eb391cc]
	.../libQt5Core.so.5(QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) 0x112)[0x7f262eade512]
	.../libQt5Core.so.5(QThread::exec() 0xb4)[0x7f262e89ecb4]
	.../libQt5Core.so.5( 0x9cd2e)[0x7f262e8a3d2e]
	.../libpthread.so.0( 0x80a4)[0x7f2632cec0a4]
	.../libc.so.6(clone 0x6d)[0x7f2631ccd04d]

Full catchsegv log:

http://qutebrowser.org:8010/builders/debian-jessie/builds/1214/steps/unittests/logs/stdio

This has been reported and fixed upstream:

https://bugreports.qt.io/browse/QTBUG-44407
https://codereview.qt-project.org/#/c/111893/

And indeed I've not seen this happen since 5.4.2.

I'd be glad if the patch could be backported:

http://code.qt.io/cgit/qt/qtbase.git/patch/?id=3f0f707d4b898a96e63e16c13a29f12be01d9b4c

Thanks,

Florian

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5network5 depends on:
ii  libc6              2.19-18+deb8u1
ii  libqt5core5a       5.3.2+dfsg-4+deb8u1
ii  libqt5dbus5        5.3.2+dfsg-4+deb8u1
ii  libstdc++6         4.9.2-10
ii  multiarch-support  2.19-18+deb8u1
ii  zlib1g             1:1.2.8.dfsg-2+b1

libqt5network5 recommends no packages.

libqt5network5 suggests no packages.

-- no debconf information