[PyQt] Segfaults when (dis)connecting signals on deleted QWebFrame
me at the-compiler.org
Wed Dec 3 06:38:04 GMT 2014
* Phil Thompson <phil at riverbankcomputing.com> [2014-12-02 22:35:25 +0000]:
> On 02/12/2014 7:30 pm, Florian Bruhin wrote:
> >Some weeks ago I had some issues with segfaults when disconnecting
> >QWebFrame::contentSizeChanged. I now finally was able to reproduce it
> >and wrote a little example script which is attached.
> >When running it, and after the output (connecting/disconnecting)
> >begins clicking any link on the page, there's a segfault with the
> >attached stacktrace. In the wild I've also seen this happen without
> >actually changing the page, but I can't reliably reproduce that.
> >What's going on there? Is this a PyQt or a Qt bug? I'd expect to get a
> >RuntimeError telling me the underlying object has been deleted by Qt.
> You will only get a RuntimeError if PyQt detects that the object has been
> deleted. It can only do this if it (rather than Qt) created the object.
Thanks, that explains what I'm seeing. I solved it by monitoring the
QObject::destroyed signal and not disconnecting the signal where the
objects were destroyed.
Though that made me curious -- what is the reason PyQt can't just
connect a slot to QObject::destroyed for each wrapper, which marks the
underlying object as dead if invoked?
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: not available
More information about the PyQt