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

List:       pykde
Subject:    Re: [PyQt] PyQt4 gc problems
From:       Phil Thompson <phil () riverbankcomputing ! co ! uk>
Date:       2007-08-31 23:32:04
Message-ID: 200709010032.04331.phil () riverbankcomputing ! co ! uk
[Download RAW message or body]

On Friday 31 August 2007, Phil Thompson wrote:
> On Friday 31 August 2007, tim blechmann wrote:
> > hi all,
> >
> > i am using PyQt4 in a multithreaded c++ application. most of the threads
> > are not created by qt, but are native threads that are managed from c++.
> >
> > so, i had quite a number of crashes, with messages like:
> >
> > ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to
> > objects owned by a different thread. Current thread b022db50. Receiver
> > 'mainWindow' (of type 'QWidget') was created in thread 83ffd10", file
> > kernel/qcoreapplication.cpp, line 269
> >
> > from what i can tell, these events are sent from the python garbage
> > collector, which is called from an arbitrary thread, that is accessing
> > python. after disabling the automatic gc and running gc.collect() from
> > the QApplication loop manually, it seems to work flawless.
> >
> > is this a known bug/feature?
> >
> > thanks, tim
>
> Try the current snapshot.

...and I should have said - and the current SIP snapshot.

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