[PyQt] Freezes and crashes with signal autoconnection

Phil Thompson phil at riverbankcomputing.com
Sun Nov 15 14:35:25 GMT 2009

On Sat, 14 Nov 2009 05:22:41 -0800 (PST), Christian Roche
<christian.roche.fr at gmail.com> wrote:
> Hi again;
> Phil Thompson-5 wrote:
>> I can't remember if you are using snapshots or not, but there are some
>> issues fixed related to looking up Python reimplementations of virtual
>> methods.
> forget about Windows. The whole thing crashes so quick on Windows XP that
> can't even get a glimpse of the main window. I'm using the latest build
> (PyQt-Py2.6-gpl-4.6.1-1.exe) but not snapshots as I can't compile there.
> I'd
> be willing to compile a build there and also get debugger feedback but I
> would need a pointer on some resource on how to do that on Windows.
> Back on Linux I also get crashes although much less frequently. The
> difference is that I'm able to get some feedback from the system in that
> case so it might prove a bit more useful! Here is the backtrace of a
> crash that appears to occur when a thread calls the QUrl.resolved()
> This is with PyQt4-4.5.4-1 and sip-4.8.2.
> -----------------------------------------
> Program terminated with signal 11, Segmentation fault.                   
> #0  0x082c0f23 in qpycore_PyObject_FromQString (qstr=@0xb5bd21b8) at
> qpycore_qstring.cpp:55                   
> 55              *pyu++ = (qstr.at(i)).unicode();                         

It's difficult to see how this would crash if everything else (ie. Python
and Qt) is working as it should.

However it does imply you are using a very old version of Qt (v4.1).


More information about the PyQt mailing list