[Development] systematic crash-on-exit in QDBusConnectionPrivate::closeConnection
René J. V. Bertin
rjvbertin at gmail.com
Tue Dec 5 17:23:05 CET 2017
Thiago Macieira wrote:
> Keep applying the patch on top of the official release.
Wasn't that clear? I'm still running 5.8 *with* the fixes.
This does look like a related-but-different issue though, trying to disconnect a
valid receiver from a sender instance which has apparently already been deleted.
It appears to be an issue caused by (with?) the QtCurve widget style, though.
FWIW, this is what I get for the receiver object:
(lldb) p ((QObject*)receiver)->dumpObjectInfo()
OBJECT QDBusConnectionPrivate::unnamed
SIGNALS OUT
signal: destroyed(QObject*)
signal: destroyed()
signal: objectNameChanged(QString)
signal: dispatchStatusChanged()
<functor or function pointer>
signal: spyHooksFinished(QDBusMessage)
<functor or function pointer>
signal: messageNeedsSending(QDBusPendingCallPrivate*,void*,int)
<functor or function pointer>
signal: messageNeedsSending(QDBusPendingCallPrivate*,void*)
signal:
signalNeedsConnecting(QString,QDBusConnectionPrivate::SignalHook)
<functor or function pointer>
signal:
signalNeedsDisconnecting(QString,QDBusConnectionPrivate::SignalHook)
<functor or function pointer>
signal: serviceOwnerChanged(QString,QString,QString)
signal: callWithCallbackFailed(QDBusError,QDBusMessage)
<functor or function pointer>
SIGNALS IN
<-- QDBusAdaptorConnector::unnamed relaySignal(QObject*,const
QMetaObject*,int,QVariantList)
<-- KHintsSettingsMac::unnamed <unknown>
<-- QDBusConnectionPrivate::unnamed <unknown>
<-- QDBusConnectionPrivate::unnamed <unknown>
<-- QDBusConnectionPrivate::unnamed <unknown>
<-- QDBusConnectionPrivate::unnamed <unknown>
<-- QDBusConnectionPrivate::unnamed <unknown>
More information about the Development
mailing list