[PyQt] Segfaults when (dis)connecting signals on deleted QWebFrame

[Phil Thompson]

On 02/12/2014 7:30 pm, Florian Bruhin wrote:
> Hi,
> 
> 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.

Phil