[PyKDE] Bad Memory Leak

Andre Reitz reitz at inworks.de
Wed Dec 6 19:24:25 GMT 2006


If I disconnect the signal after exec_loop() then
the leak does not occur.

I Just found out that in fact in Version 4.1 the leak does 
not occur.

Greetings and thanks for all


from qt import *
def c():
	print "cc"

while 1:
	QObject.disconnect(b,sss,c) #<<-- no more leak now
	del b
	del d

Andreas Pakulat wrote:
> On 06.12.06 16:04:24, Andre Reitz wrote:
>> Sounds great,
>> but memory usage increases continuously.
>> Do you have an idea why?
>> Is there a bug on C++/SIP side?
> Maybe, but as Giovanni said, this is not reproducible with
> not-so-ancient PyQt versions, so the solution for you is to upgrade PyQt
> and sip.
> BTW: What happens if you first disconnect the signal and then delete the
> dialog?
> And last but not least: The Windows task tracker is not a sufficient
> tool to find memory leaks. On Linux I'd suggest to use valgrind, but I
> don't know which tools are available for Windows.
> Andreas



Als Technologie- und Beratungsunternehmen entwickeln und implementieren
wir standardisierte IT-Lösungen zum Kunden- und Mitarbeitermanagement.

Mit dem Intrafox® Complaint Manager bieten wir die Standardsoftware
für professionelles Beschwerdemanagement an. Mehr unter www.intrafox.de

Der Inquery® Survey Server ist eine der leistungsfähigsten Lösungen
für Online-Umfragen - z.B. für Kunden- oder Mitarbeiterbefragungen.
Mehr unter www.inquery.de

Inworks GmbH
Andre Reitz, Leiter Entwicklung
Hörvelsinger Weg 39, D - 89081 Ulm
Tel +49 731 93807-21
Fax +49 731 93807-18

Internet: http://www.inworks.de

More information about the PyQt mailing list