[PyKDE] PyQT Memory Leak (new)
Nahuel Greco
nahuel at puntorojo.com.ar
Wed Mar 23 15:51:41 GMT 2005
Hi, I think that I have found a memory leak in the latest PyQT snapshot. When you
create forms, if the form constructor connects their signals, after his destruction
a "weakref" object remains in memory. Note the attached logs:
without_signal_connections.log: For this log I only pressed the second button,
so the forms were created without connecting their signals. Python objects count
remains constant, as you can see in the gc debug messages. Also the memory used
don't increases.
connecting_signals.log: Here I only pressed the first button, the forms were
created connecting their signals. This case leaks, the memory increased after
each run, and you can see in the gc debug messages that for each created form
an object of type 'weakref' remains without beign collected.
Saludos,
Nahuel Greco.
Saludos,
Nahuel Greco.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: without_signal_connections.log
Type: application/octet-stream
Size: 3810 bytes
Desc: not available
Url : http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20050323/4d7a4bfb/without_signal_connections.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: connecting_signals.log
Type: application/octet-stream
Size: 5447 bytes
Desc: not available
Url : http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20050323/4d7a4bfb/connecting_signals.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: isolate_new_leak.py
Type: text/x-python
Size: 4220 bytes
Desc: not available
Url : http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20050323/4d7a4bfb/isolate_new_leak.py
More information about the PyQt
mailing list