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

List:       pykde
Subject:    Re: [PyQt] Segfault: QGraphicsView, cyclic references, and threads
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2011-03-28 21:58:40
Message-ID: fcc1c37d752b2ba72cdce87d9e79821e () localhost
[Download RAW message or body]

On Mon, 28 Mar 2011 22:36:02 +0200, Erik Janssens
<Erik.Janssens@conceptive.be> wrote:
> I can confirm the issue in pyqt 4.8.3 / qt 4.7.2
> 
> it segfaults, but with the following assert statement :
> 
> .QObject::killTimers: timers cannot be stopped from another thread
> ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to
> objects owned by a different thread. Current thread b6b08490. Receiver
> 'qt_scrollarea_hcontainer' (of type 'QWidget') was created in thread
> 94eeee8", file kernel/qcoreapplication.cpp, line 349
> 
> 
> Phil,
> 
> does this mean that a QGraphicsScene is only garbage collected
> when the QApplication has been garbage collected, thus creating
> a memory leak ?

No.

It just means that any QGraphicsScene instances that haven't been garbage
collected are guaranteed to be destroyed before the QApplication.

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]