[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] Deadlock in QPyQmlObjectProxy::disconnectNotify
From:       Arjen Hiemstra <a.hiemstra () ultimaker ! com>
Date:       2016-03-14 14:49:50
Message-ID: 5261408.aQ46rmEebf () ultargash
[Download RAW message or body]

On Saturday, 12 March 2016 23:01:04 CET Phil Thompson wrote:
> > 
> >> This seems to be a timing issue rather than a logic issue. What I will
> >> probably do is just to remove the disconnectNotify() implementation on
> >> the assumption that, if the signal has been disconnected, then it's
> >> never going to be emitted. In any event I think the only time the signal
> >> will be disconnected is when the internal Qml sender is being destroyed.> 
> > Is this something I could patch locally to help test it? Just remove
> > the implementation of disconnectNotify in qpyqmlobject.cpp ?
> 
> Yes - and from the .h file.
> 
> Or use the snapshot.

Thanks Phil. Removing disconnectNotify seems to do the trick and fix the 
deadlock.

- Arjen

> 
> Phil


_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]