Hello all, not really sure if I
am right here with my problem, but there is a
great Memoryleak:
from qt import *
app=QApplication([])
def c():
print "cc"
sss=SIGNAL("clicked()")
while 1:
d=QDialog()
b=QPushButton("x",d)
Q(b,sss,c) #<
d.exec_loop()
del b
del d
Stay on the escape key, so that many many dialogs
will be created and deleted.
Watch used Memory and you will see it increases
significantly.
If you comment aut the marked line (Q)
then the problem does not occur.
Problem occurs on linux (PyQt-3.5.1-19 (SuSE))
and on Windows (PyQt-3.11 and PyQt-3.14)
Greetings, Andre'
PyKDE mailing list PyKDE (AT) mats (DOT) imk.fraunhofer.de

Thank you for your quick answer

Sounds great,
but memory usage increases continuously.
Do you have an idea why?
Is there a bug on C++/SIP side?

Greetings, Andre'

Here agaign the test code:

Please watch Memory usage in Windows Task-Manager
while holding down the ESCAPE-Key, so you will
see the mem-usage of the process grows.
If you remove the Q() line
it will *not* grow.

My Problem is that we are developing a large long running
application in PyQt and we would have plenty of these leaks.

from qt import *
app=QApplication([])
def c():
print "cc"

sss=SIGNAL("clicked()")
while 1:
d=QDialog()
b=QPushButton("x",d)
Q(b,sss,c) #<
d.exec_loop()
del b
del d

Giovanni Bajo wrote:
Andreas Pakulat wrote:

>Note this is python, not C++, del foobar doesn't immediately free the
>memory associated.

That's incorrect. "del foobar" removes a reference; if it's the last
reference and there are no loops, the memory is immediately collected. Now,
there are no reference loops at the Python level, so the memory *is*
collected when the "del" statement is executed.

Specifically, the first "del b" collected the Python-side instance of the
push button (the Cside of the pushbutton is owned by the dialog as it's a
chiled). The second "del d" collects the Python-side instance of the dialog,
which in turns causes a deletion of the Cside of the dialog (since it has
no parent, so it's fully owned by Python); the C++ destructor also destroys
the Cside of the pushbutton. So, after the second "del", all the memory
is reclaimed, with no need for the Python cyclic GC to kick in.

PyKDE mailing list PyKDE (AT) mats (DOT) imk.fraunhofer.de